Is there a better way to saved linked information than window procedural variable?

pcsoft.us.windevCopyright 2026, PC SOFT27 Jan 2016 21:32:24 Z27 Jan 2016 21:32:24 ZI have two tables that are linked with a child / parent relationship using the parent id field in the table analysis. Index Books |__Index Book Group Browsing the index books - pressing "Modify" button on an Index Book opens up linked Index Book Groups [code:wl] Open(WIN_IndexGroups_Browse, IndexBooks.IndexBooksID) [/code] Inserting a new Index Book Group uses this code to save the new Index Book Group with the parent ID. [code:wl] ScreenToFile() // If it's a new record IF IndexGroups..NewRecord = True THEN IndexGroups.IndexBooksID = WIN_IndexGroups_Browse.pIndexBooksID HAdd(IndexGroups) ELSE HModify(IndexGroups) END // Return value of the window MyWindow..ReturnedValue = True [/code] This feels dirty to me. Am I missing something - is there a better way to do this by specifying new edit records should inherit linked parent record fields?30WEBDEVen_UShttps://forum.pcsoft.fr/es-ES/pcsoft.us.windev/56093-there-better-way-saved-linked-information-than-window/read.awpIs there a better way to saved linked information than window procedural variable?moderateur@pcsoft.fr (El moderador)webmaster@pcsoft.fr (El webmaster)