How to check for db lock

[John K]

I have a database that is on 20 different laptops that go into the field.
When they return to the office they upload to a master copy of the database
on the server. The process is just simple append queries. The problem
occurs when someone may have the "master" copy open or another user is trying
an upload.

The question is, how can I set up a test to check for connectivity before
they try to hit the buttons that run the append queries?

 

[Wayne-I-M]

Have a look at the answer given by Pieter Wijnen


http://groups.google.com/group/micr...roup:microsoft.public.access#a8b3f91b035c87a7

 

[John K]

Thank you, the link has some great resources but is not quite what I hoped for.

I have a macro that runs the updates and it will error if someone else is in
the database or another user is appending their records at the time. The
users are not technically proficient so I was looking for a way to have their
copy (remote, connected to network via cisco vpn) of the database check for
connectivity first and give them basically a go/no go type reponse and then
they can hit the next button. They are only transferring small amounts of
data so the process takes less than 20-30 seconds.

 

[Wayne-I-M]

I tend to take the simple way (where possible).

If it were me I would check that no-one is using the system and then make
the changes.

 

[Wayne-I-M]

Oh - just thought

Why not write a little code - via a delete or append - that would (after you
have done your "stuff") check for updates - via a select - then if the select
says there was an update then rerun. Very simple but it would work