Hello,
I have a split multi-user DB in Access 2000. I'm usind edited record-locking and as far as I understand it, if two people are editing the same record, it will save the changes of whoever does so first and the second person who tries to change will get a write conflict error with the options to 'Save Changes', 'Copy To Clipboard', and 'Drop Changes'(there is no error #).
Testing this out on two machines, when I get the write conflict as the second person to update the record, I found that if I choose 'Save Changes', it appears to have saved my changes, but when I try to change records (using DoCmd.goToRecord), nothing happens. So I try to PgUp or PgDn and I get a message (not an error) from Access saying "The record cannot be deleted or changes because table 'TABLENAME' contains related records". This makes no sense to me since TABLENAME has nothing to do with the record being updated except for its key (The Table the form is based off and TABLENAME have a one-to-many relationship, respectively).
What I really want to be able to do is give the option to the second person who updated to truly save their changes if they feel so inclined. I would also like to get rid of the write conflict message in some way for it seems to really screw things up for me. I've read every post here almost on record-locking and write-conflicts and except for maybe editing my registry, I have no idea why it wont accept 'Save Changes' as an acceptable choice. I would really appreciate any help anyone had to give on this subject. Thanx. (^_^)
-Jedi420
A man who has risked his life knows that careers are worthless, and a man who will not risk his career has a worthless life.
I have a split multi-user DB in Access 2000. I'm usind edited record-locking and as far as I understand it, if two people are editing the same record, it will save the changes of whoever does so first and the second person who tries to change will get a write conflict error with the options to 'Save Changes', 'Copy To Clipboard', and 'Drop Changes'(there is no error #).
Testing this out on two machines, when I get the write conflict as the second person to update the record, I found that if I choose 'Save Changes', it appears to have saved my changes, but when I try to change records (using DoCmd.goToRecord), nothing happens. So I try to PgUp or PgDn and I get a message (not an error) from Access saying "The record cannot be deleted or changes because table 'TABLENAME' contains related records". This makes no sense to me since TABLENAME has nothing to do with the record being updated except for its key (The Table the form is based off and TABLENAME have a one-to-many relationship, respectively).
What I really want to be able to do is give the option to the second person who updated to truly save their changes if they feel so inclined. I would also like to get rid of the write conflict message in some way for it seems to really screw things up for me. I've read every post here almost on record-locking and write-conflicts and except for maybe editing my registry, I have no idea why it wont accept 'Save Changes' as an acceptable choice. I would really appreciate any help anyone had to give on this subject. Thanx. (^_^)
-Jedi420
A man who has risked his life knows that careers are worthless, and a man who will not risk his career has a worthless life.
