You can manage transactions in an AppServer session much the same way that you can manage them in an ABL client session, using transaction blocks and statements that update tables in a database. However, because client and AppServer sessions are entirely separate, including their transaction contexts, the client normally has no direct ability to influence the course of an AppServer transaction, which begins and ends within the scope of a single remote procedure request. To allow finer-grained control of transactions running on the AppServer, OpenEdge provides an additional transaction type that allows a transaction on the AppServer to span multiple client requests.
