Cannot open my own database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I created a db last on Friday sitting at someone else's computer, logged in
as myself using Windows 2003. I put user-level security on the db with myself
in the admin group. I saved it to my network drive, then shut the db down and
tried to re-open to test, but it said I did not have permission. Eventually I
discovered that if I opened it one certain way, it would open, but I don't
remember what worked.
I came in this morning on my own computer again, logged in as myself, and I
cannot find any way that will let me into my own db. Any idea why I'm having
problems having the db recognize me as myself? I could open the backup (and I
can), but I did some additional work on the real db without saving to the
backup and I'd like to not lose it.
 
Your windows login name is not relevant.

When you set up security on the other person's computer, you created a mdw
file - it sounds as though you didn't copy that to the server along with the
mdb.

Once you have the secured mdw copied to the server, you can create a desktop
shortcut to start your secure mdb. The target of the shortcut would look
like
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure.mdw"
 
It did not create issuestracking.mdw, no. It *did* create security.mdw, which
is with the rest of the files, but it only lists the usergroups and who is in
them, and it cannot be edited.
But if the system does not capture Windows logon, how does it know who you
are - how would user-level security work?
 
I found the answer on another forum. For those of you who run into the same
thing, the .mdw that Access sets up when you create your user groups in the
security wizard is not always the .mdw Access wants to look at. Go to
Tools/Security/Workgroup Administrator and join the .mdw that was created and
should be sitting in the same folder that your .mdb is in (not system.mdw
which is the default).
 
Actually you do not want to do that. Using the workgroup administrator,
you'll set your secure mdw to be the default. That means you'll be prompted
for username/password for all sessions of Access, not just your secure mdb.

You are better off leaving the default as system.mdw, and using the desktop
shortcut for your secure mdb.
 
Back
Top