Re: More security questions

You shouldn't be logging in as Admin, since that user doesn't (shouldn't)
have permissions to do anything. You just wanted to set a password for this
user so that the login dialog would appear.

You now want to log in as the user that owns the database.

Usernames/passwords/group membership are stored in the mdw. Permissions are
stored in the mdb. So your various backups may have different permissions on
the objects.

No I am not an employee of MS.

--
Joan Wild
Microsoft Access MVP


"Joe G" wrote:

Double checked the case sensitivity...none of the backups are working. I
don't get the permissions tab enabled, even though I log in as Admin.
Are the user names stored in the MDB or the MDW ? All of my backups at this
point had been using the same security MDW. I am assuming that this MDW is
the correct one because I see users listed. Are you an employee of
Microsoft, Joan ?
I am relatively knew to MS Access. I have been developing with PowerBuilder
for the last ten plus years. Again. Appreciate the help.

Joe

"Joan Wild" wrote:

Remember that passwords are case sensitive.

Since this started when you restored a backup, perhaps that backup doesn't
have the permissions set correctly. When you check the owner tab in the
permissions dialog, what user is listed as owner of everything?

--
Joan Wild
Microsoft Access MVP


"Joe G" wrote:

OK. Changed the password for admin, but then get the same message that I
don't have the necessary permissions. Cannot change the password for user
Joe, who also had admin rights when I created the secured database. His
password is not blank nor is it what I thought it was.

"Joan Wild" wrote:

OK, so you know you are using security.mdw, but you get no login. That means
that the Admin password is currently blank. Go into the Accounts dialog and
change password tab. Set a password for the Admin user (remember that the
old password is blank).

Close Access and try your shortcut again.
--
Joan Wild
Microsoft Access MVP


"Joe G" wrote:

Joan,
I mis-stated one thing below. My MDB is BladeRunner.MDB which is in a
directory under MyDocuments\BladeRunner. The security file is Security.mdw
and there is a Security.ldb all in the same directory. I created a shortcut
but when I launch, I get the same permission message.

I am by default using the secured mdw:

? dbEngine.SystemDb
C:\Documents and Settings\Joe\My Documents\BladeRunner\Security.mdw

I am still not prompted for a password, but appear to be logged on as Admin.
I cannot change the admin password, and it tells me that the old password is
incorrect. I see the users that I created, but cannot change those passwords
or get prompted to log in.

I am sure confused and getting nervous about this...I have invested a large
chunk of time in this development effort, and sure hope you can help me
understand what I've done here. Thanks again for your help.

Joe





"Joan Wild" wrote:

"Joe G" wrote:

Hello Joan !

I have an MDB file that I secured a few weeks back which was working fine.
I did something yesterday when I unzipped a backup copy of the database
(although I unzipped it to a different directory) that has caused me problems.

I have an MDW file of the same name as the MDB, residing in the same
directory.

That's not a good idea. Both the mdb and the mdw need to create an
associated ldb file. They can't if they have the same name. Rename the mdw
file (and then modify any shortcuts as necessary).

I join the workgroup for the MDB - which has the two users that I created
when I secured the database, but when I try to open the database, I get the
message about not having the necessary permission and to contact the system
admin.

Are you certain you have joined the correct mdw file?

I am thinking that I am logged in as the universal admin (since I am not
prompted for a password) and am wondering how I go about trying to log in as
the user I had created when I secured the database who has amin permissions.
I am not being prompted to log in as I used to be.

When you open Access, go to Workgroup Administrator and verify the mdw you
are using by default. It should be the standard system.mdw that ships with
Access. Use a desktop shortcut to launch your secure mdb.
"path to msaccess.exe" "path to mdb" /wrkgrp "path to mdw"

When you launch via the shortcut, you should get a login prompt. If you
don't then perhaps you've somehow cleared the password for the 'Admin' user
or your shortcut has a problem, in which case it will use system.mdw. In
either case hit Ctrl-G and type DbEngine.SystemDB which will tell you the mdw
it is *using*.

If it is your secure mdw then go to Tools, security, accounts, password tab
- it will show you that you are logged in as Admin - set a password for this
user.

If it is the system.mdw then your shortcut has an error in it.

--
Joan Wild
Microsoft Access MVP

.

Relevant Pages

  • Re: More security questions
    ... this thread your question was seen for sure by Joan Wild and Lynn Trapp. ... have permissions to do anything. ... Usernames/passwords/group membership are stored in the mdw. ... Microsoft Access MVP ...
    (microsoft.public.access.security)
  • Re: More security questions
    ... "Joe G" wrote: ... have permissions to do anything. ... Usernames/passwords/group membership are stored in the mdw. ... Microsoft Access MVP ...
    (microsoft.public.access.security)
  • Re: More security questions
    ... have permissions to do anything. ... Usernames/passwords/group membership are stored in the mdw. ... Microsoft Access MVP ... who also had admin rights when I created the secured database. ...
    (microsoft.public.access.security)
  • Re: More security questions
    ... have the permissions set correctly. ... who also had admin rights when I created the secured database. ... Close Access and try your shortcut again. ... I have an MDW file of the same name as the MDB, ...
    (microsoft.public.access.security)
  • Re: More security questions
    ... have permissions to do anything. ... Usernames/passwords/group membership are stored in the mdw. ... Microsoft Access MVP ... who also had admin rights when I created the secured database. ...
    (microsoft.public.access.security)