My application uses Access as the front end to SQL7. I open a form and start a new workspace. Then I start a new Transaction. One of the first things to take place is for the user to select a bunch of records and my code sets a lock on each record. Then the user starts another process and I start another transaction. If the transaction completes ok I (.Committ) the transaction, if not (.Rollback.) The problem is when I encounter a bug or what ever, and need to kill the app to shut it down. My first transaction in the workspace which never got a chance to see (.Committ) still ends up saving the data in the table! Any idea why it is able to committ the data without the command? [sig]<p>John A. Gilman<br><a href=mailto:gms@uslink.net>gms@uslink.net</a><br>[/sig]
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
New Workspace and New Transaction question
- Thread starter jagilman
- Start date
Jagilman, you might try floating your question in the Access forum. It sounds like it is more Access related than SQL Server. [sig]<p>Robert Bradley<br><a href=mailto: > </a><br><a href= - Visual FoxPro Development</a><br> [/sig]
- Status
Similar threads
- Locked
- Question