Split DB - Record Locking File

[teachme]

I am building a multi user DB and need to know what are the best practices to handle the record locking file.

The locking file for back end database is I dont care about for the front end, is there a way to hide it so the user doesnt see it?

In the past I have created a folder somewhere in the hard drive of the user's machine and then placed a short cut on the desktop. This way when the user runs the application on the desktop, they dont see the record locking file because it is created where the actual file is located.

Is the the right way of handling this?

Thank you

 

[RuralGuy]

Are you using a URL name to get to your BE? If not, why not?

 

[arnelgp]

what is record locking file?
you can burry the fe in a folder and create a shortcut on desktop.

 

[teachme]

Are you using a URL name to get to your BE? If not, why not?

Sorry, I have no idea what that means

 

[teachme]

you can burry the fe in a folder and create a shortcut on desktop.

Yup, that is what I am thinking about doing.

 

[sneuberg]

Sorry, I have no idea what that means

Maybe he meant UNC but I'd like to know what's wrong with mapped drive locations.

 

[teachme]

I'd like to know what's wrong with mapped drive locations.

Sorry, I dont know what you mean

 

[sneuberg]

Sorry, I dont know what you mean

Sorry I didn't expect you to. That was intended more for RuralGuy. I should have made that clear.

 

[Galaxiom]

Maybe he meant UNC

Maybe, but Access can actually link tables using a URL too.

I'd like to know what's wrong with mapped drive locations.

Mainly that they rely on users having the appropriate drive mapping in place.

I use a UNC path to a hidden share (append share name with a $) and a domain group policy to turn off UNC browsing so the users only see the mapped drives.