Back End on a Server

[Novice1]

If a split a database and placed the back end on a shared server, would the users of the front end need Read/Write access of the folder contained the back end on the shared drive? Note: Users need to add, delete and edit records.

I'm trying to figure out a way that the user cannot go to the server and copy the back end (little more security).

 

[AccessBlaster]

I'm trying to figure out a way that the user cannot go to the server and copy the back end (little more security).

You can try and keep honest people out. If you lock the nav pane then compile to mde or accde it might help. Caution you could lock yourself out.

 

[Galaxiom]

One way is to put the backend on a hidden share. (Simply append a dollar sign to the sharename when you configure it.)

Then prevent users from browsing UNC paths. Of course this potentially restricts their other activities too.

 

[pbaldy]

would the users of the front end need Read/Write access of the folder contained the back end on the shared drive?

And the answer to this question is yes.

 

[The_Doc_Man]

In general, users need the Windows "MODIFY" class of permissions on the folder because of the lock file. The rule is that users must be able to READ and WRITE records in the database and lock files, but... the first user to open a BE file needs to be able to CREATE the lock file and the last user to close the BE file needs to be able to DELETE the lock file. This equates to Windows "MODIFY" permissions.