I have a replicated database (one replica) that I now need to secure with
User-Level security. I just plan on using the wizard. I have secured in this
manner before without trouble, but I have not done it on a replicated
database. Is there anything different I need to know before plunging in? Do I
need to run the wizard on both the master and replica, or just the master
then synchronize?

It isn't entirely clear from your description, but it sounds like you
have not split the database.  Replication is intended for data only (not
forms/reports etc).

It is imperative that you split the mdb.  The backend (contains only
tables/relationships) would be the only thing you replicate.  The
frontend (contains all other objects) would have linked tables (linked
to the backend) and be located on each person's computer.

Joan Wild
MS Access MVP

Mrs. Ugh wrote:
Show quoteHide quote

=?Utf-8?B?TXJzLiBVZ2g=?= <Mrs***@discussions.microsoft.com> wrote in
Joan cautioned you on splitting, and her advice is spot-on. You
don't have to do anything fancy to split a replicated app, just
import the non-tables into a new MDB, delete the non-tables from
your Design Master, and then in the new MDB, link to the tables in
your back end replica.

Now, as to user-level security, you're not going to like the answer.

No, you can't apply it to individual replicas. It has to be applied
to the Design Master. That doesn't sound so bad, right? Well,
unfortunately, it is -- you can't secure a pre-existing Design
Master in any meaningful sense of the term "secure." What you're
going to have to do is unreplicate your back end, run the security
wizard on it, and then re-replicate it.

Otherwise, the top-level database object will be accessible to
everyone, and that's a hole a mile wide that can be used to get
access to all the data.

Sorry the answer is not better.

For unreplicating, see the Question 10 of the Jet Replication Wiki:

  http://dfenton.com/DFA/Replication/index.php?title=FAQ

You'll want to coordinate with your users and synch up the whole
replica set before you unreplicate, and tell them to stop using the
the database while you're recreating the secured replica set.

BE/ FE Question
vba opendatabase readonly
Linking to a password protected BE from FE
record level lock access 2002
Security Problem When Linking Tables
can't disable shift key with faq_DisableShiftKeyBypass function
Secure part of a db?
recordset not updatabale
Other methods for preventing "not have exclusive access at this time" message?
Maintaining and updating Access 2007 database