This document summarises the points at which you can easily customise gui integration behaviour.
There are a number of protected virtual methods provided in the helper classes. Simply override these methods to provide your own processing.
CLASS dbEditHelper
EnteringAboutToLoad()
- Called just before copying record values into controls. Controls should be fully constructed at this point, by the mechanism specific to the particular GUI, and probably initialised to default values.
EnteringAfterLoad()
- Called after record values are loaded into controls. If you have any unlinked controls which have values derived from the database values, this is where you'd set them. (Alternatively, once we implement virtual fields, you could have a virtual field linked to the control.)
CanLeaveRecord
- Called by all movement buttons and OK button. Default allows departure from record but you can override for complex validation.
LeavingAboutToSave()
- Called just before copying the values back to the fields, from the various edit controls.
LeavingAfterSave()
- Called immediately after the record has been saved to the database, but before the record is unloaded or the context changes in any way. Changes to the edit controls at this point would NOT be saved.
