Hello to anyone out there,
Most people seem to be struggling with writing conflicts in multiple user access applications, but our issue is just the opposite.
We work with a large database and we want a few users (max. 5 to 6 at the worst) to be able to edit tables at the same time by using forms. We have split the database into front end and back end. The BE is placed on a NAS and each user had an offline copy of the FE on his own desktop.
All users have full permissions and we switched the options (client settings -> Advanced) to the following settings:
Default open mode: Shared
Default record locking: Edited record
Open databases by using record-level locking: yes
Encryption method: use legacy encryption (good for multi-user databases).
In the forms we also changed the property ‘record locks’ to ‘edited record’.
What we wanted to achieve is that when a user changes a certain record in a form, other users can’t change the same record until the changes of the first user are saved. This would mean that we would see a lock icon in the selector bar, as mentioned in this forum:
https://stackoverflow.com/questions...ing-a-record-in-multi-user-access-environment
For the moment we have done several tests, but we are unable to generate any “Writing conflict” when implementing the above, contrary to the numerous reports on the opposite behaviour one can find reported in the internet and the documentation of Access. The first user changes a record and the second user is still able to change it, without any particular notification in the sense of a selector bar icon or a “writing conflict”, and the user that closes the database the latest takes it all (all changes by the first user are overruled).
If there would be anyone out there who managed to overcome a similar issue, it would be great if you could share your experience.
Thanks in advance,
Wim
Most people seem to be struggling with writing conflicts in multiple user access applications, but our issue is just the opposite.
We work with a large database and we want a few users (max. 5 to 6 at the worst) to be able to edit tables at the same time by using forms. We have split the database into front end and back end. The BE is placed on a NAS and each user had an offline copy of the FE on his own desktop.
All users have full permissions and we switched the options (client settings -> Advanced) to the following settings:
Default open mode: Shared
Default record locking: Edited record
Open databases by using record-level locking: yes
Encryption method: use legacy encryption (good for multi-user databases).
In the forms we also changed the property ‘record locks’ to ‘edited record’.
What we wanted to achieve is that when a user changes a certain record in a form, other users can’t change the same record until the changes of the first user are saved. This would mean that we would see a lock icon in the selector bar, as mentioned in this forum:
https://stackoverflow.com/questions...ing-a-record-in-multi-user-access-environment
For the moment we have done several tests, but we are unable to generate any “Writing conflict” when implementing the above, contrary to the numerous reports on the opposite behaviour one can find reported in the internet and the documentation of Access. The first user changes a record and the second user is still able to change it, without any particular notification in the sense of a selector bar icon or a “writing conflict”, and the user that closes the database the latest takes it all (all changes by the first user are overruled).
If there would be anyone out there who managed to overcome a similar issue, it would be great if you could share your experience.
Thanks in advance,
Wim