I have an unbound form in an Access project that sets it's RecordSource to an ADO recordset in the OnLoad event. On the form's Dirty event, I start a new transaction on the connection object (if one hasn't already been started). When the user exits the form, I can prompt them to save or discard the changes, and issue a commit or rollback.
Everything works except this:
When the user moves off the current record, after editing a field, I can commit or rollback just fine. However, if the user stays on the current record they've just edited, but moves to another field, trying to issue a Rollback doesn't work, and the data is committed no matter what!
Thoughts, suggestions?
Everything works except this:
When the user moves off the current record, after editing a field, I can commit or rollback just fine. However, if the user stays on the current record they've just edited, but moves to another field, trying to issue a Rollback doesn't work, and the data is committed no matter what!
Thoughts, suggestions?
