Par2: Field priming with Edit in Place 1998-04-28 -- Nik Johnson The ultimate add/change/delete is done by the RelationManager for the browse's primary file. Assuming that the primary file for a browse is MyFile, adds will be done by ACCESS:MyFile.INSERT, changes by RELATE:MyFile.UPDATE and deletes by RELATE:MyFile.DELETE. If your calculation/field priming applies to every update, put them in the Access/RELATE:MyFile classes themselves. You can add to (override) the methods of these classes in the Globabl embed of your main (or data DLL) app. If your calculations apply only when Edit-in-Place is used, you may have to override the .AskRecord method for the browse. This is a large and complex method, avoid fooling with it if possible. If your calculations can be triggered by the completion of a particular field, you could put the code in the TakeEvent method of the Edit-in-Place class derived for that field. Printed November 21, 2024, 11:47 am This article has been viewed/printed 35185 times. |