Hi Andrew,
It is just my idea and may not be necessary for others. Here it is,
When defining an Access/Browse control inside of a controller, normally the developers would need triggers such as
On_Insert, On_Delete, On_Modify on the record level to interact with user actions to perform data validation and other type of business logic. Furthermore, the developers would also need triggers such as On_Validate on a field level to interact with users to do similar tasks.
Mostly of the similar triggers are already provided in suneido controls, but require additional actions to be added into controller. Sometimes, it takes a lot of time and effort to figure out how they should be defined or if they exist at all. So my idea is that, it would be a good practice to add them into the controller as a standard step when defining controller.
When I look at them later, I can see immediately what triggers are available and use them accordingly. It is also easier for other developers to do continuous support and modification.