Secruity problem

[Guest]

First off, let me apoligize if this question has been asked and answered
before. I usually try to search a forum first, but wasn't quick sure what to
search by in this case!

I have used the Secruity Wizard in Access to add start-up passwords to one
database (A). That seems to have worked fine.

My problem is that 'it' seems to have added passwords to all my Access
database files. (I have three seperate databases (A, B, C) on my computer
because I work for three projects - only one needs to protected). That would
be semi-okay (although annoying), except that when I try and use the password
I set up when securing A (and have typed it correctly according to the
Wizard's Report) it does not work on B or C. I'm just locked out of those
two.

It seems strange that I would have to add permissions to all my databases
when I only want to do one. Is there a way around it?

I double checked the permissions etc. in database A and I don't seem to have
inadvertantly included anything that shouldn't be there...

Thanks!

 

[Guest]

Follow-up, when I enter the password for database A into B or C I get this
error message: Not a valid account name or password

 

[Joan Wild]

You don't mention the version, but it's possible that the wizard has made your secure mdw the default one to use for all sessions.

Do a search on your computer for all *.mdw files and note their paths. Open Access, and use Tools, security, workgroup administrator - this will tell you what your current default is set to. It should be system.mdw - the workgroup file that ships with Access. Click on Join and rejoin this workgroup. Now every session will use the standard system.mdw and not require a login.

For your secure mdb, create a desktop shortcut to start the mdb - (the wizard may have created one for you).

It's target would have the following in it
"path to msaccess.exe" "path to secure mdb" /wrkgrp "path to secure mdw"

When you open your unsecure databases, it will use the default system.mdw instead.

 

[Guest]

Thanks Joan,

I am using Access 2003.
As suggested, I did a search, the .mdw file created by the wizard was the
only one, and the Workgroup Administrator had it as the appropriate file. I
'joined' this workgroup.

I am still having the problem of not being able to open my other databases.

Any other suggestions? I am working on an organizational network. Would
this make a difference?

Shortcut was created by wizard, as you said.

 

[Guest]

I think I've fixed it. the file search didn't bring up the second
system.mdw, but I stumbled across it this morning and now is seems as if all
databases are working as they should. hopefully it stays like that!

 

[Guest]

Hi All

I was having the same problem. I wanted security on one of my databases but
not on the other but when i encrypted my one it required i "login" to access
before i could use any of them. I couldn't figure out how to undo what i did
and reading this i got the idea to search for the system.mdw on another
computer and i just did a copy paste and that gave me full access to
everything again. I'm not sure if that was the most elegant way to do it or
if i'm going to run into problems later but it's working today for me.

The question i would like to pose to people. All i want to do is create a
login page to my database before poeple can open it. Eventually i want to be
able to assign permissions such and read/write but for now if i can just
achieve a open/not open login i'd be happy.

--Mike

 

[Joan Wild]

You don't mention the version, but look at
www.jmwild.com/AccessSecurity.htm
for detailed steps to securing your database

 

[Guest]

I will look at that page a bit later. Thanks for the link.

I think I may have a problem because our network resets the C Drive
everynight and puts that system.mdw back each time. Depending on what your
article says, I may just have to find someother way to secure the
information.

 

[Joan Wild]

That really shouldn't matter. You want the system.mdw that ships with Access to be set as your default. Use a desktop shortcut for your secure mdb with a target of
"path to msaccess.exe" "path to secure mdb" /wrkgrp "path to secure mdw"