Securing Backend Files via NTFS

stuartk

Registered User.
Local time
Today, 10:09
Joined
Oct 19, 2010
Messages
19
Hi All

Most of our staff are not IT professionals and I have noticed that some of them have been opening the database backend (stored on server shared folder) rather than their database frontend (stored in My Documents).

Obviously this creates problems and can damage the databases.

So is there any way to lock down the backend folders via NTFS permissions but still enable the users to have functionality?

Regards
 
If you put a check in your opening form that gets the currentproject.path and if it is not C: then boot them off with a DoCmd.Quit
 
If you put a check in your opening form that gets the currentproject.path and if it is not C: then boot them off with a DoCmd.Quit

Hi Buddy

Sorry thats way over my head.

Do you know any clear, step by step guides?

Regards
 
It can't be more simpler...

Go to the Open Load Event of the startup form and enter the following code:

Code:
If Left(CurrentProject.Path,1) <> "C" Then
   Msgbox "You cannot open the application from the server. Use the copy on your local machine.",VbCritial,VbOkOnly,"Access Denied"
   DoCmd.Quit
End If
 
Hi Buddy

Sorry for being a total twit but I do not know where:

Open Load Event

Is located

Regards
 
Desing your start up form and got to the properties of the form and look for On Load. Click on the elipses button [...] to go to the event and paste the code there.
 
Desing your start up form and got to the properties of the form and look for On Load. Click on the elipses button [...] to go to the event and paste the code there.

Still lost!

Is this on the FE or BE?

Regards
 
FRONT END.

You should have realised that when the fix takes about startup forms.

The CurrentProject.Path variant is the full path and file name of the file being opened. So if the user attempts to open the app that is stored on the server the first letter will be the drive letter and if it is not "C" Local machine then it knows that they are opening the app from somewhre other than the correct one.
 
OK I understand.

But I'm as to where to enter your code!

Also what if the user navigates to the backend folder on the server and opens that?

Regards
 
If you put a check in your opening form that gets the currentproject.path and if it is not C: then boot them off with a DoCmd.Quit

That will only work if the backend has a form that is opened when the backend is opened. Maybe an AutoExec macro to call a custom function with the above code from DCrake would be best for the backend to keep the users from opening the backend.
 
Hi All

Most of our staff are not IT professionals and I have noticed that some of them have been opening the database backend (stored on server shared folder) rather than their database frontend (stored in My Documents).

Obviously this creates problems and can damage the databases.

So is there any way to lock down the backend folders via NTFS permissions but still enable the users to have functionality?

Regards
The BE database should only contain tables and not be of interest to non-IT people. Each user should have their own copy of the FE database with forms, queries, reports etc. Is this the way your DB is set up?

There is no need of the users to know where the BE is located or what it is called. This info should be built into the FE.
 
Put an on open password on the back end. Then relink all the tables from the front end to the back end. You will be asked for the password but it will be embedded with the table links and the users will not be able to see the password if they try to look inside the front end.
 

Users who are viewing this thread

Back
Top Bottom