Secure a Single DB

Stigm@t@

Registered User.
Local time
Today, 20:05
Joined
Sep 11, 2006
Messages
10
Hey

I am looking for a way to secure a single DB. I would like to be able to use the DB on other PC, but still have user control.

I have found that when using the MS Access User and Ground way will only secure DB's used on the PC it was set on. If i take the DB to my home PC i am not promted for a Password and i can go mad with information i would like to protect.

Am i doing something wrong when setting the security? :confused:

Shot
 
When you set the security for an Access database, the settings are stored in a file. The default name is System.mdw
System.mdw is normally found in the Windows system folder.
When you transfer the database to a different computer the System.mdw is not transfered. As a result, no security for the database on the new computer (no security settings in System.mdw on computer 2).
The trick is to store the database in its own folder, create a 2nd .mdw file (not named System) and store it in the same folder. Then use the 2nd .mdw for that database.
 
Hey statsman

That sounds good, but if the DB is then moved to another PC that does not have this second .mdw file, will anyone be able to open or will it not open as it does not have the specified .mdw file.

This security part of access is new to me, i have never had a need for it before until now, thus i am sorry if asking stupid questions.
 
First, security works with the Workgroup file. You must have the workgroup file to maintain the securiyt.

Second, the last workgroup file you joined is a REGISTRY setting. You must join the workgroup from whatever machine you are using.

Third, search this forum for tips on securing a database via workgroup.
 
Hey Doc

I have been looking through the threads and have found a lot of information regarding security. However i have not found anything that is quite what i am looking for.

I think that a good start for what i need to do, can be done using the Disable Shift Key function that Ghudson posted. I do still need user level control that for lack of a better word is unique to the DB and is basically a stand-alone.

Would using a unique .mdw file do this?
 
Stigm@t@ said:
Hey Doc

I have been looking through the threads and have found a lot of information regarding security. However i have not found anything that is quite what i am looking for.

I think that a good start for what i need to do, can be done using the Disable Shift Key function that Ghudson posted. I do still need user level control that for lack of a better word is unique to the DB and is basically a stand-alone.

Would using a unique .mdw file do this?
I don't know if this will answer your question, but it's worth to take a look at:

http://www.access-programmers.co.uk/forums/showthread.php?t=113298

Hope this helps.
 
Thanks Bee

But i have already read that thread. I just read something else that makes me think that i will not be able to do what i would like to.

Would the following statement be true?

When you start a DB up you are prompted to logon. Once you have, you will not be able to change who is logged on without closing the DB and opening it again.

If true, is there a method to use to get around this.
 
Stigm@t@ said:
Thanks Bee

But i have already read that thread. I just read something else that makes me think that i will not be able to do what i would like to.

Would the following statement be true?

When you start a DB up you are prompted to logon. Once you have, you will not be able to change who is logged on without closing the DB and opening it again.

If true, is there a method to use to get around this.
Hi Stigm@t@,

I don't know the answer to your question, but good luck.

Regards,
B
 
Ghudson

Hey

I am trying to get hold of Ghudson. How can i do this. I tried to message but the message box is full.
 
Hey Ion

Please can you pass the information that you spoke of to me. I think that if i can get my hands on as much information as possible, it may help me understand the Access Security.

Tanks
 

Users who are viewing this thread

Back
Top Bottom