record locking on backend db

[Jim Shaw]

BlankI have an application which has a back-end database. I will soon be
moving it to multi-user use.
Do I set up record locking in the back-end db, or should I set it up in the
front-end database?

Thanks
Jim

 

[Allen Browne]

This is an Access database, and you have already split it so that the tables
are in a separate mdb, linked to your front end mdb?

If so, there is nothing extra you have to do to make the database
multi-user. Just give each user their own local copy of the front end. Leave
the locking on Optimisitic (also called No Locks), and train the users to
handle the conflict dialog. In many cases, the data entry people say they
never see this dialog, but they should know how to handle it if they do see
it.

 

[Jim Shaw]

Yes this is an Access 2002 database.
I split the database several months ago before I got to the part in my
Writing VBA Code book about multi-users and record locking issues.
I assume your response is valid for that circumstance; but I hope it also
holds for supporting multiple users running on a Citrix Server.

Thanks,
Jim

 

[Allen Browne]

I don't see a problem, provided each user has their own copy of the front
end. It will be stored in their own space on the server of course, but the
important thing is individual front ends.