By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,757 Members | 1,990 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,757 IT Pros & Developers. It's quick & easy.

Securing an Access Database.

P: n/a
D
If you secure an MSACCESS Database using a Workgroup Information File
WIF and then setting up permissions removing the Admin user from the
its default group, repalce it with another named user, transfer all
the ownership of objects to the new user. Then run the database
security wizard. If after this the mdb file is placed on a different
users PC which is still using the defauult system.mdw file should they
still be able to open the database with full rights and permissions ?

May 7 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
D wrote:
If you secure an MSACCESS Database using a Workgroup Information File
WIF and then setting up permissions removing the Admin user from the
its default group, repalce it with another named user, transfer all
the ownership of objects to the new user. Then run the database
security wizard. If after this the mdb file is placed on a different
users PC which is still using the defauult system.mdw file should they
still be able to open the database with full rights and permissions ?
No. If they can you missed a step.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com
May 7 '07 #2

P: n/a
Hi, David.
If after this the mdb file is placed on a different
users PC which is still using the defauult system.mdw file should they
still be able to open the database with full rights and permissions ?
In many cases, yes, but only if certain vital steps were missed. To give
you an idea of which steps were missed, even after taking those steps you
described, the database will not be secured under any of the following
circumstances:

1.) The workgroup information file used to secure the database is the
default workgroup information file.

2.) The owner of the database is the default Admin user, even if the owner
is later changed to another user.

3.) The owner of all the objects is originally the default Admin user, even
if ownership is later transferred to another user.

4.) The Access 2000 Security Wizard is used to secure the database.

5.) The Users group has permissions to open and run the database.

6.) Any member of the Admins group doesn't have a password set, or the
password is easily guessed.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.
"D" <da***********@virgin.netwrote in message
news:g6********************************@4ax.com...
If you secure an MSACCESS Database using a Workgroup Information File
WIF and then setting up permissions removing the Admin user from the
its default group, repalce it with another named user, transfer all
the ownership of objects to the new user. Then run the database
security wizard. If after this the mdb file is placed on a different
users PC which is still using the defauult system.mdw file should they
still be able to open the database with full rights and permissions ?

May 7 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.