Secure Database

[Guest]

I am trying to set up a secure database. I have created a new workgroup, and
open a blank database, however, it still defaults to ADMIN as the owner of
the new database. How can I change this default so that I am the owner of
this database? I am trying to set up users and permission, but I need to own
the database in order to properly protect it. I don't know how to create a
new database where Admin is not the owner.

 

[Joseph Meehan]

I am trying to set up a secure database. I have created a new
workgroup, and open a blank database, however, it still defaults to
ADMIN as the owner of the new database. How can I change this default
so that I am the owner of this database? I am trying to set up users
and permission, but I need to own the database in order to properly
protect it. I don't know how to create a new database where Admin is
not the owner.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can easily lock
you out of your database, which might require the paid services of a
professional to help you get back in.

Practice on some copies to make sure you know what you are doing.

 

[Joan Wild]

I am trying to set up a secure database. I have created a new workgroup,
and
open a blank database, however, it still defaults to ADMIN as the owner of
the new database.

You need to create a new workgroup.
Create a new user
Add this user to the Admins Group
Remove Admin user from the Admins Group
Set a password for the Admin User.
Close Access.
Open Access
Create a new database
Supply the 'new user' name with a blank password.
Now this new database will be owned by the 'new user'

Following these steps will ensure that you are logged in as the 'new user'
when you create the new database.

 

[Guest]

Yes, I have already downloaded and read the information from that link. I
have been able to set up my users and permissions, however, it is not
completely secure because I cannot change the default on the owner of the
database. I am setting up a blank database on a travel drive. After I
complete getting the owner/users/groups and permissions set up, I will import
information to that drive and make sure everything works properly from there.
My problem at this point seems to be not having Admin as the owner of the
database. I have opened Access and set up a new workgroup file name, but
when I open a blank database, it still lists ADMIN as the owner and I don't
know how to change this. I need to be the owner or I cannot property secure
it.
--
Ronnie

I am trying to set up a secure database. I have created a new
workgroup, and open a blank database, however, it still defaults to
ADMIN as the owner of the new database. How can I change this default
so that I am the owner of this database? I am trying to set up users
and permission, but I need to own the database in order to properly
protect it. I don't know how to create a new database where Admin is
not the owner.

I suggest you start by reading
http://support.microsoft.com/default.aspx?scid=kb;[LN];207793

Access security is a great feature, but it is, by nature a complex product
with a very steep learning curve. Properly used it offers very safe
versatile protection and control. However a simple mistake can easily lock
you out of your database, which might require the paid services of a
professional to help you get back in.

Practice on some copies to make sure you know what you are doing.

 

[Guest]

I have followed the instructions in the "Access 2002/2003 Security Steb by
Step" creating a new workgroup, new user (me), added used to Admins Group,
removed Admin User from the Admins Group, set password for the Admin User,
closed and reopened Access with the log-in under my name. However, when I
create the new database, "Admin" is still listed as the owner and I am unable
to change this.

 

[Joan Wild]

I have followed the instructions in the "Access 2002/2003 Security Steb by
Step" creating a new workgroup, new user (me), added used to Admins
Group,
removed Admin User from the Admins Group, set password for the Admin User,
closed and reopened Access with the log-in under my name. However, when I
create the new database, "Admin" is still listed as the owner and I am
unable
to change this.

After you ...set password for the Admin User, and close Access, and then
reopen Access...
Hit Ctrl-G and type
?DbEngine.SystemDB
and hit enter
That should display the path to your new workgroup file - Does it? Try
?CurrentUser()
and hit enter
That should display the username you logged in as.

If the workgroup is correct, and the current user is correct, create a new
database and check the owner.

If the workgroup isn't correct, then you can start your Access session with
a desktop shortcut that has the following in the target:
"path to msaccess.exe" /wrkgrp "path to new workgroup you created"

 

[Guest]

I have check the workgroup file and that I am logged in as the user. Both
are correct. I created a new database and Admin is still the owner.

 

[Joan Wild]

Sorry Ronnie, but I have *never* heard of that. If you are logged in as a
user named 'Bill' and you create a new database, 'Bill' is the owner of the
database object.

If you like, zip up the mdw you are using, and the mdb you tried to create
and email them to me with the username you're using.
jwild at tyenet dot com

 

[John W. Vinson]

I have followed the instructions in the "Access 2002/2003 Security Steb by
Step" creating a new workgroup, new user (me), added used to Admins Group,
removed Admin User from the Admins Group, set password for the Admin User,
closed and reopened Access with the log-in under my name. However, when I
create the new database, "Admin" is still listed as the owner and I am unable
to change this.

You can probably fix this. Log on with your new ID; open the database;
select Tools... Security... User and Group Permissions, and select the
"Change Owner" tab.

John W. Vinson [MVP]

 

[Joan Wild]

You can probably fix this. Log on with your new ID; open the database;
select Tools... Security... User and Group Permissions, and select the
"Change Owner" tab.

Won't work John. You cannot change the owner of the database object using
the dialog (every other object you can, but not the database object).

 

[Guest]

Thanks! I'll try that!
--
Ronnie

Sorry Ronnie, but I have *never* heard of that. If you are logged in as a
user named 'Bill' and you create a new database, 'Bill' is the owner of the
database object.

If you like, zip up the mdw you are using, and the mdb you tried to create
and email them to me with the username you're using.
jwild at tyenet dot com

 

[Guest]

Unfortunately, the "change owner" tab is not available when Admin is the
owner of the database.

 

[John W. Vinson]

Won't work John. You cannot change the owner of the database object using
the dialog (every other object you can, but not the database object).

ahhh.... right. Thanks Joan and apologies, Ronnie!

John W. Vinson [MVP]

 

[Joan Wild]

Ronnie,

I received the mdw file and I had no problem creating a mdb owned by a user
other than Admin.

Steps I took:
I created a desktop shortcut that has the following in the target:
"C:\Program Files\Microsoft Office\Office10\msaccess.exe" /wrkgrp
"C:\testing\RGB workgroup.mdw"
(that's all on one line. I am using Access 2002. Your shortcut would look
similar, but the path to the workgroup would be different, and if you are
using a different version of Access, the path to msaccess.exe would be
different)

I double-click the shortcut which will open Access using the RGB
workgroup.mdw workgroup. I clicked on New and chose Blank Database.

The login dialog pops up and I enter the username/password you gave me. The
new databaes is created. To check the owner, I went to Tools, security,
user and group permissions and click on the 'Change Owner' tab. In the
object type combo, I chose Database. It lists the database object and the
username is correct - it isn't Admin.
Is this not what you see?