Colm said:
That indicates that the workgroup you are currently using, was not the same
one that was used to secure it with.
when i ran the wizard i accepted the default setiing
The default setting may have been 'create a new workgroup' if you were
currently joined by default to system.mdw. If you were joined to a secure
mdw when you ran the wizard, then there were two options - create a new one,
or modify existing (the default). If you chose to modify the existing then
you were not modifying the system.mdw.
Security.mdw C:\Documents and Settings\colm\My Documents\Databases
SYSTEM.mdw C:\cquinn ltop\program files\microsoft office\office
SBCMTMPL.mdw C:\cquinn ltop\program files\microsoft
office\office\SBT\SBCM
Open Access (no mdb need be open). Go to Tools, Security, Workgroup
Administrator. It will show you the workgroup you are currently joined to
by default. Try joining one of the other ones (likely security.mdw). Open
your database to see if you can now log in and see the owner of the objects.
If not then try joining the sbcmtmpl.mdw workgroup.
Access always uses the default mdw (as set in tools, security, workgroup
administrator). If the 'Admin' user has a password set in this workgroup,
you will get a login prompt, regardless of the database you open. When you
run the security wizard, it will create a desktop shortcut to launch your
database. This shortcut specifies a workgroup file to use (bypassing the
default one). So one normally leaves their computer joined by default to
the standard system.mdw and uses shortcuts to open secure databases. All
other sessions of Access will use the default system.mdw and get no login.
Your best option at this point, would be to determine which workgroup was
used to secure your database (as above). Then rejoin the standard
system.mdw (assuming you didn't actually modify this). Then create a
desktop shortcut to start your secure database. The target would look like:
"path to msaccess.exe" "path to mdb" /wrkgrp "path to secure mdw"
Once you are using the correct workgroup, any user you make a member of the
Admins group can 'administer' the database.