MDW problems

[G1ZmO]

I know this has been asked loads of times. I've read many posts and still can't seem to get the grip of this.

I have a few databases in a shared location on our server at work.

The new database is to hold network passwords, user details etc and therefore has to be secure. Only 1 administrative login is required.

Here are the filenames:
CompanySecurity.mdb
SECURITY.mdw
I have a shortcut file as:
"C:\Program Files\Microsoft Office\OFFICE11\MSACCESS.EXE" "\\NETWORKLOCATION\CompanySecurity.mdb" /wrkgrp "\\NETWORKLOCATION\SECURITY.mdw"

The Admin account still exists in the mdw file but the ownership rights of most of the database have been passed to the "Secure" administrative user. I cannot seem to delete the Admin account btw.

Now, If I run the shortcut it works fine and I can log in with the credentials set in the mdw file. Username: Secure (with password)

However, If I just open the CompanySecurity.mdb file it just opens without requesting a password etc. btw it opens from a machine with Access Runtime only installed also. My other mdb file in the same folder does the same incidentally though security isnt a big concern for that db.

I know everyone keeps saying you need to open a db using a shortcut but what is to stop a user from browsing to the network location and opening the mdb file?

Wouldnt it be easier and more secure just to set a password on the mdb? and do away with the mdw file?

Thanks

Paul

 

[Len Boorman]

send me a PM with an email address and I can send a couple of docs that explain security. Will not be able to send until this evening.

Len

 

[G1ZmO]

Many thanks Len

I have solved the security problems with that db now.

Another related question though:

If I am to properly secure my other databases I need to change the owner to the SuperUser and remove permissions from Admin so...

If the DBs are currently split, do I have to unsplit them before importing all the data into a new DB (where SuperUser will be the owner) ?

(Going to use the same mdw for all the databases btw)

Thanks

Paul

 

[Len Boorman]

Now you have got me
I really do not know
Suggest a search on Security and see what turns up.

There are piles of threads on this and it may take a while but the answer is probably there

Sorry cannot help from here

My suspicion is that you make the FE open and secure the BE but I could be very wrong

Len

 

[G1ZmO]

Yes, I think you're right that the BE should be secured and the FE open but I'm just not sure whether I'll have to unsplit first as fixing the security will mean changing the owner of both FE and BE.

 

[Len Boorman]

Done some checking

It seems

Secure the BE. tight
Secure the FE no changes to design of anything

Take copies (One more than you think you will need) and play on your C drive

Len