Multi-User Dataentry

[DanG]

Here's the scenerio...
I'm in my database on a particular record after having entered data into it and I have not exited out or moved to a new record. Then another user comes into this same record and enters data into the record I'm in. If go to exit out of the database or start a now record or whatever, I get an error telling me I can't save changes, do I want to copy record into the clipboard...

I have gone to tools>advanced>default recordlocking and set it to "edited record" and I still have this problem?

Any ideas?

 

[MStef]

Tell me smoe more details.
What is the primary key in this table ? (Data Type).
Do you, and another user work on a NEW record ?
What is the message exact ??

 

[gemma-the-husky]

access is inherently multi user

if there is a possiblity that two users can access the same record at the same time, and you dont want this, then you can institute recordlocking - and this should definitely work - however there are drawbacks, as this can cause performance issues - eg, a user locks a record, then goes to lunch ...

access always uses a form of locking anyway - it just uses something called optimistic locking, which assumes that there wont be any problems, but it rereads the record before writing your changes to see if it can still be updated

this is why you are getting your error - access is telling you , while you were using the record somebody else changed it, so it is now unsafe for you to save it. As i say, tyhe alternative would prevent the other user being able to access the record until you were done with it - but doing this can seriously impair the user experience - ie in your case the other guy wouldnt be able to do anything until you finished dealing with the record - and this could cascade into other areas, preventing reports etc, that needed to use your locked records.

because of all this, you need to be careful when using record locking, and try and lock records for the minimum time necessary. so implementation of record locking needs careful planning.

 

[Fifty2One]

access is inherently multi user

if there is a possiblity that two users can access the same record at the same time, and you dont want this, then you can institute recordlocking - and this should definitely work - however there are drawbacks, as this can cause performance issues - eg, a user locks a record, then goes to lunch ...

If you use the record locking you can put a Close Form statement under the On Timer Event and set the Timer Interval for a reasonable amount of time. Obviously if someone is on a fill in or update form for more then a couple of minutes they have drifted off to sleep, left their workstation or gone for lunch.

 

[DanG]

access is inherently multi user

if there is a possiblity that two users can access the same record at the same time, and you dont want this, then you can institute recordlocking - and this should definitely work - however there are drawbacks, as this can cause performance issues - eg, a user locks a record, then goes to lunch ...

access always uses a form of locking anyway - it just uses something called optimistic locking, which assumes that there wont be any problems, but it rereads the record before writing your changes to see if it can still be updated

this is why you are getting your error - access is telling you , while you were using the record somebody else changed it, so it is now unsafe for you to save it. As i say, tyhe alternative would prevent the other user being able to access the record until you were done with it - but doing this can seriously impair the user experience - ie in your case the other guy wouldnt be able to do anything until you finished dealing with the record - and this could cascade into other areas, preventing reports etc, that needed to use your locked records.

because of all this, you need to be careful when using record locking, and try and lock records for the minimum time necessary. so implementation of record locking needs careful planning.

I have read about this a little bit and I think this is the problem. How do you change the record locking?

I understand your warnings and will look for other solutions first (like time-outs).

Thank you all very much!