For some reason, I am not the Owner of my back-end database, which prevents
me from setting any permissions regarding new objects.

Is there a way to recover from this?

Thank you.
Sprinks

Sprinks wrote:
The owner isn't the only user who can set permissions on objects.  You just
need to log into the database as a member of the Admins group to set
permissions.  But your description prompts a question.

When you check the current owner of <Current Database>, does it say <Unknown>,
or does it say another user's name?  If it's <Unknown>, then that means
you've logged into a database that was created using a different workgroup
file, but it wasn't secured properly (which is very common).  If it were
secured properly, then you wouldn't have been able to open it while joined to
a different workgroup.  If another user's name is listed as the owner, then
you just need to log into the database as that user to have the owner's
privileges again.

Granny,

It says "Unknown" which means I have not secured it properly.  Can you tell
me how to do so?

Sprinks

Show quoteHide quote

Join your custom workgroup, create a new db file and import the objects from
the other file into it.

Keith.
www.keithwilby.com

Thanks, Keith.

Sprinks

Show quoteHide quote

Sprinks wrote:
First, find the *right* workgroup file.  You may need to search the hard
drive or even the network for it.  When you find it, create a shortcut for it
(if you don't already have one) so you can open the database while joined to
that workgroup during that session only.  The syntax for the shortcut would
be like this (this is all one line):

"C:\Program Files\Microsoft Office\OFFICE10\MSACCESS.EXE" C:\Database.mdb
/wrkgrp C:\Secure\Secure.MDW

Open the database as the owner (you should be prompted for user name and
password), and check the permissions for the Database object type.  Open/Run,
Open Exclusive, and Administer should be unchecked for the Users group and
the default Admin user, and the Admin user should have been removed from the
Admins group.

If you used the Access 2000 security wizard to secure the database, the Users
group will still have permissions, because there's a bug in this wizard that
didn't get fixed until Access 2002.  If this is the case, then you'll need to
remove the permissions on all objects for the Users group.  The simplest way
to do this if you have a lot of objects and you only have two groups (the
Admins and Users groups) is to create a new database file while logged in as
the owner you want to own the database and set all new objects' permissions
so that the Users group doesn't have any.  Remove the permission to Open/Run,
Open Exclusive, and Administer the Database object from the Users group, then
import the objects from the old database into the new database.

If you have additional groups to set their permissions on the objects, then
you might want to avoid creating a new database.  Just keep the objects in
the original database and only remove the permissions from the Users group if
this is less work than the alternative.

Once you fix these permissions, check to ensure that the Admins group (and
any other group that needs access to the database) has permission to Open/Run,
Open Exclusive, and Administer the Database object.  (The Admins group
doesn't always need "Open Exclusive," so use your best judgement on this.)
Now close Access and try to open the file again while joined to the other
workgroup file (which is probably your default System.MDW file).  You should
receive an error message that you don't have permission to open the secure
database (because you're currently joined to the wrong workgroup), which is
what you want to happen.

Post back if you still have problems, hon.

MDW locks, cant add/modify users
Security Problem with Adobe 7.0
problem with a batch file wkgrp parameter
Record-Locking
Security nightmare
Make mdb Read Only in code?
Default CurrentUser when not opening form
shortcut just to access
How do I retrieve a User PID
Removing Security from One MDB