Stored Procedures and Transactions
It is a good idea to place transactions in all of the stored procedures that you build. Transactions ensure that a piece of work is completed in its entirety or not at all. One of the classic examples is a banking transaction. You want all the debits and credits to complete properly or not at all. This is where transactions come in.
You might have used the BEGINTRANS, COMMITTRANS, and ROLLBACK methods in data access objects (DAOs) going against Access data. These DAO methods are appropriate when going against an Access back end. When using a SQL Server back end, you should instead place all transaction processing inside the stored procedures that you build.
Types of Transactions
Two types of transactions exist: ...
Get Alison Balter's Mastering Access 2002 Enterprise Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
