WinStudio
Tip: Processing Subcollection Saves
Save operations in forms with subcollections are handled in a single
network round trip or in multiple round trips, depending on the framework
version.
Version 6.0 and Later
In version 6.0 and later, IDO items (rows) in the top-level collection
and in each subcollection are saved in one network round trip. In
a form without custom event handlers, the sequence is as follows:
- The StdObjectSave event is generated for the top-level
collection.
- For each modified subcollection, the StdObjectSave event
is generated for the subcollection.
- All top-level and subcollection inserts, updates, and deletes
are sent to the server for processing.
- For each modified subcollection, the StdObjectSaveCompleted
event is generated for the subcollection.
- The StdObjectSaveCompleted event is generated for the
top-level collection.
Versions Earlier Than 6.0
In versions earlier than 6.0, subcollection saves are performed
in multiple round trips.
- The StdObjectSave event is generated for the top-level
collection.
- Inserts and updates of IDO items in the top-level collection
are sent to the server for processing.
- For each modified subcollection,
- The StdObjectSave event is generated for the subcollection.
- Inserts, updates, and deletes of IDO items in the subcollection
are sent to the server for processing.
- The StdObjectSaveCompleted event is generated for
the subcollection.
- Deletes of IDO items in the top-level collection are sent to
the server for processing.
- The StdObjectSaveCompleted event is generated for the
top-level collection.
Related Topics
Edit
Collection Specification for Subcollection Dialog Box
Tip:
Referencing Collections Bound to Forms or Grids
Tip: Refreshing Collections
Understanding
Forms with Subcollections