"Read Only" error locks out SOME users

I have a VBA front-end database used by many soldiers around the world. The
database uses linked tables. Each user has a copy of the back end in the
same folder as the front end.

Some (not all) users get a "read only" message when they open the front end
(VBA database), and because the read only lock it won't update the links the
in database causing it to not function.

None of the files are set to "read only".

The whole package works on all the computers in my local area at work and I
have not been able to recreate the problem there so it has been hard to
trouble shoot.
(Running Office XP with SP2)

Installing a fresh version of MS Office XP with out the service packs at
home did recreate the error. This leads me to think that this problem may be
linked to the version of access being used.

Does anyone have any suggestions on how to solve the problem?

Thanks,
JR

Check the permissions of the folder holding the database files. They need
read, write, create, and delete permissions for both the mdb files AND the
entire folder.

Also with the databases closed, check to see if there are any .ldb files in
the folder with the same name as the databases. Delete these .ldb files.

Not very likely but possible is that they are actually opening up the
database as read only.

Another shot in the dark is to temporary disable any virus checkers on those
problem computers.
--
Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"JR" wrote:

I have a VBA front-end database used by many soldiers around the world. The
database uses linked tables. Each user has a copy of the back end in the
same folder as the front end.

Some (not all) users get a "read only" message when they open the front end
(VBA database), and because the read only lock it won't update the links the
in database causing it to not function.

None of the files are set to "read only".

The whole package works on all the computers in my local area at work and I
have not been able to recreate the problem there so it has been hard to
trouble shoot.
(Running Office XP with SP2)

Installing a fresh version of MS Office XP with out the service packs at
home did recreate the error. This leads me to think that this problem may be
linked to the version of access being used.

Does anyone have any suggestions on how to solve the problem?

Thanks,
JR