WinStudio
Occurs before WinStudio sends all changed object data in a collection or subcollection to the middle-tier IDO, which commits the changes to the SQL Server database. The event occurs during execution of one of the following:
The default implementation of the StdFormSave event
An event handler of the type Collection Save
The Save method in a script
The default implementation fires the following sequence of standard events:
StdObjectSave
StdObjectSaveCompleted
Your application cannot call the default implementation by generating the event.
The default implementation is a collection-level operation, which can occur in a collection whether or not the collection is current.
The StdObjectSave event is fired once for each collection and subcollection in a Save operation. The event allows the developer to determine what action to perform at the start of a Save for a top-level collection and for each subcollection.
The event is not fired for each row in a collection or subcollection. An event handler intended to operate on each row in response to a row-level event should not be assigned to the StdObjectSave event. Instead, to process rows, an event handler on StdObjectSave must loop through all modified rows in the current top-level collection and all subcollections.
An event handler that performs row-level validations should normally be assigned to the StdFormPerformValidations event.
Tip: Processing Subcollection Saves