Transaction Mode and Sybase Versions Previous to 11.9.2

See Also

Sybase does not support row-level locking. This could cause problems in a multi-user environment, because as each data manipulation is sent to the RDBMS immediately, locks must be maintained on all rows affected until a commit or rollback is performed.

In USoft Developer for Sybase, the conceptual server provides a transaction mode, in which all data manipulations performed by a user are sent to the kernel at commit-time. This greatly reduces the time during which rows must be locked. If the transaction fails, a rollback is sent to the RDBMS. Immediate feedback is returned for referential integrity, and cascading update and deletes are executed normally, even if the row has yet to be stored in the kernel.

Transaction mode is activated by setting a Behavior property of the application in the Windows Designer:

TransactionMode : BatchManipulation