Just when I thought . . .

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

Guest

I had user level security in place and working nicely. Upon splitting my
database, my custom created group that had limited permissions before now
have no permissions at all on the front end. Also, the default users group
has full permissions to the backend when they had none in the original
database. What gives?

Rip
 
Hi.
the default users group
has full permissions to the backend when they had none in the original
database. What gives?
Click to expand...

You used the Database Splitter Wizard _after_ you applied user-level
security. This wizard ignores user-level security, so the security
permissions you so carefully applied to the original database file do not
propagate to the newly-created file.

For an easy way to split the database after applying user-level security,
try the following steps:

1.) Back up the original, secured database file.
2.) Copy the original database file to the network shared directory where
the back end needs to be.
3.) Join the secure workgroup either before or while opening the original
database file, which will become the front end. Make sure you log in as a
user who has sufficient permissions for deleting, creating, and modifying
tables.
4.) Delete the tables in the front end database file and then link to the
tables located in the back end database file.
5.) Distribute copies of the new front end database file to the users'
workstations.

You may also want to take a look at Sandra Daigle's (Access MVP) utility for
copying the security permissions of another database file. Please see the
following Web page:

http://www.daiglenet.com/MSAccess.htm

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
 
Back
Top