regarding the locking file

[Guest]

Split db
the back end is in a folder with a large number of other files.
I want the user to have access to the db through their front-end by allowing
creating/sharing/deleting/etc for the back end file.
I also apply it to the locking file.
but once that locking file is deleted people can't get back into the
database since it appears that there is a "new" locking file, so they don't
have rights.
It will involve a lot of time/cost to change where the front end is looking
on everyone's db since most are remote users, so I'm looking for another
alternative to just moving the back end to it's own folder and giving
everyone rights to that folder.
is there anyway to give rights to a locking file, and keep them applied?

Thanks

 

[Guest]

No. The users need to create and delete the locking file. If they can't only
one person can be in the database at once.

How about moving all the other files out of the folder instead?

 

[Guest]

Yes, you can remove the delete right from the locking file.

Without the delete right, no one will be able to get exclusive
access to the database, so you won't be able to make
design changes.

Also, if you ever get database corruption, you will need to
remember to delete the locking file.

(david)

 

[Guest]

Yeah, that's my last option since it will involve quite a bit of time to
switch everyone's front-end.

Currently, on each front-end desktop, I have two files. One file (initial
file) looks at a random table in the BE in order to find the location of the
nework FE. It then saves a newer version of the FE to the desktop and opens
the FE.
So, obviously I can just change where the FE looks if I move the location of
the BE.
However, the only way to change where the initial file looks, is to go onto
each person's desktop and change it manually.

So....

If I just keep a dummy BE file under the same name, to allow the initial
file to look at in order to find the network FE, will there be any
locking/rights issues?

What I need to know is, if a user only has rights to the dummy BE file and
the network FE file, will this work to allow him to still update his FE file?

This will allow me to put the BE file in its own folder.

Sorry if this sounds confusing.


Thanks for the help so far.