Data-event handlers deal with delegates exposed on every table. These delegates are listed under the Events node.
These events do not fire if the associated method (for example, insert) is overridden on the table and super() is not called.
How event handler methods are organized is up to the developer, but they do need to be placed logically so that others will find them easily. A good naming convention (from experience) is to use the following convention: TableName_Project_DataHandler, so in our case it would be SalesConfirmHeaderTmp_ConVMSSalesReports_DataHandler.
It would be tempting to name it ConVMSSalesReportsDataHandlers, and stick them all in one class, but when we eventually have many projects with data-events, it can get hard to see what events are firing. Having one class for all table events means that it becomes a library class, and our...
