How to Avoid Locking Issues In Ms Access
How to sort out the locking issues in MS access , we have a client who is running a supermarket , they have 5 cashiers who will be accessing the same receipt form , now I'm worried about the locking issues. How can I deal with the locking system so that all the 5 cashiers will able to use the same form and save data at same time otherwise if the other cashiers have to start waiting for one cashier to save data I'm afraid there will huge ques in the supermarket. All the 5 cashiers will have their own FE and the BE will be on their server and will be accessed through the network by all.
Regards
Chris
Regards
Chris
Winch strategy is better for this scenario no lock or pesmistic
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In other words:
Go for default settings first.
Go for default settings first.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ste5an,
With a bound form, Access controls the cursor and it would never be a snapshot since that would preclude editing any of the records on the form.
Chirs,
Forms don't store data. Tables store data. As the others have said, as long as each user has his own personal copy of the FE, they are NOT using the same form. They are each using THEIR COPY of the form.
Also, pessimistic locking is more likely to cause locking conflicts rather than avoiding them assuming you are using Jet/ACE on the BE. When using an RDBMS, none of the locking settings in Access affect anything. Locking is controlled by the server.
With a bound form, Access controls the cursor and it would never be a snapshot since that would preclude editing any of the records on the form.
Chirs,
Forms don't store data. Tables store data. As the others have said, as long as each user has his own personal copy of the FE, they are NOT using the same form. They are each using THEIR COPY of the form.
Also, pessimistic locking is more likely to cause locking conflicts rather than avoiding them assuming you are using Jet/ACE on the BE. When using an RDBMS, none of the locking settings in Access affect anything. Locking is controlled by the server.
Thanks
If for some reason something goes wrong you can always go for the unbound scenario...just remove the Recordsource from the receipt form ...pull what ever data you need to populate ...and finally just push the records to the BE...
With a bound form, Access controls the cursor and it would never be a snapshot since that would preclude editing any of the records on the form.I was referring to read-only forms :) Cause read-only, continuous forms may cause locks when not being a client side cursor.
Most apps that use Access FE's use only bound forms. Why write all that code if you don't need to? Access is a RAD (Rapid Application Development) tool. If you are not going to use the RAD capabilities, there is little point of taking on the distribution, version issues, and other limitations of Access. If you are going to write all the code to manage forms yourself, you are much better off using a different platform. Access is excellent for a certain subset of client/server data-centric applications. In fact, there is nothing better. It is not however, a universal tool.
As for potential conflicts when saving data, there are no generic answer, it is all up to the data model design and the policies you want to implement.