Can you close a recordset in a nested transaction, and still be able to roll it back if the main transaction is rolled back?
In order to keep my database consistent when a user makes changes, I need to Undo all previous updates, and then Update with the new information. I capture the old data using the Current Event of the Record, and I check for a new record by using a Boolean field I created in my table. I need to ensure that all previously entered (false) information is removed, and new information is updated before I accept the update.
The problem I am having is that 4 different tables are accessed, and, depending on the circumstances, between 6 and 18 different recordsets are used. I want to be able to re-use some of the recordsets, since keeping track of open objects that need to be closed at the end of the procedure is becoming increasingly difficult.
Any help would be appreciated, and any ideas on how to do this more efficiently would also help.
Thanks
Duane Barker
In order to keep my database consistent when a user makes changes, I need to Undo all previous updates, and then Update with the new information. I capture the old data using the Current Event of the Record, and I check for a new record by using a Boolean field I created in my table. I need to ensure that all previously entered (false) information is removed, and new information is updated before I accept the update.
The problem I am having is that 4 different tables are accessed, and, depending on the circumstances, between 6 and 18 different recordsets are used. I want to be able to re-use some of the recordsets, since keeping track of open objects that need to be closed at the end of the procedure is becoming increasingly difficult.
Any help would be appreciated, and any ideas on how to do this more efficiently would also help.
Thanks
Duane Barker
