Back End Security

[adamburton]

Hi,

I have a database which is secured via a workgroup.

I have just ran the database splitter to seperate the data into a back end. But now I can open the back-end directly without any password.

How do I ensure that the back end is still secured when doing this?

Thanks,
Adam.

 

[ghudson]

If the front end is secured but the backend is not...

Rename the back end, copy the front end, rename the front end copy to the name you want for the back end. Import the objects from the old back end into the new [secured] back end. Relink the front end to the new back end.

You should be opening the front end and the back end [when needed] with a shortcut that points to where the workgroup file is located. Like this...

"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" /wrkgrp "X:\WorkgroupFile.mdw" "X:\DatabaseFile.mdb" /user UserName

 

[adamburton]

Thanks

Thanks GHudson,

Will this mean that the front end is now not secure? I understand that the user will bypass this if using the shortcut, but what if they try to open the front end database directly?

kind regards,
Adam.

 

[frozbie]

Works perfectly!

Thanks GHudson!

I searched the forum having found myself in exactly the same situation. I followed your instructions and now both my front end application and back end database are secured using the same workgroup file.

It seems to me that to further secure the back end database I could perform a similar operation but use a different front end and workgroup file and so create a separate set of passwords to directly access the back end application. But perhaps that would just create more administration

Of course by following your instructions I now have the full application available while working in the back end database which makes it a bit easier (So long as I don't forget to recreate the relationships!)

Cheers

Frozbie

 

[RCurtin]

Shortcut works but how to prevent users accessing DB directly?

Hi,
I have a database with a backend on the server and a front end on the local drive. I've created a workgroup file called DrawingsDB.mdw and put that on the server. (I intend to put this on the local drive for each user having read about this on the forum). I've created a shortcut on the desktop that opens the database and joins the user to the workgroup file. That works fine. However you can still open access and open the front end or the backend on the server no problem with no security?

How can I prevent this? I understand that the default System.mdw lets someone log on with Admin permissions. I haven't changed the System.mdw file because I don't want to affect any other databases that the users will be using? I'd really appreciate any tips. I've been reading about this all day but still can't figure out what I should be doing.

 

[ghudson]

You need to remove the Admin permissions from your custom workgroup file. Do not touch the System.mdw file. Make backups of your files for you could lock yourself out if you mess up. Search around for there are tons of postings related to your question.