Hello,

I have a database that i have 5-6 replications of on a company intranet.  I
want to be able to protect the replicates by not allowing the user access to
the back end to mess with the queries forms and reports.  I still need to be
able to work with my Master as well as I would like to be able to update the
replicates.  I have not used any of the security features at all before, so
this is all new.

I am using access 2007, but have developed a 2002-2003 mdb file format as
everyone else uses Access 2003.

any help would be appreciated.  thanks in advanced

Ryan

=?Utf-8?B?Unlpcw==?= <R***@discussions.microsoft.com> wrote in
Just to clarify:

You have an MDB of which you have created replicas using Jet
Replication, either programmatically, or through the Access user
interface?

This is very confusing to me, as a back end should have tables only,
and not queries or forms or reports. And in the case of replication,
you shouldn't be replicating anything but the data tables (i.e., the
back end), as Jet replication eventually fails with front end
objects (forms/reports/etc.).

With this you add even more confusion, as replication and security
are two completely different subjects that don't overlap at all.

I'm going to answer based on a guess that your database is unsplit
(i.e., one MDB with tables and forms/reports/queries) and that it is
replicated so that each of your users on your "Intranet" can edit
and synch data. In that scenario, your question would be how to edit
forms/reports/queries in something other than the Design Master.

The answer is that you can't.

But the solution is quite simple:

Split your app -- it's a necessity in 99% of Access applications,
but for replicated apps, it's a 100% necessity as replication
eventually corrupts front-end objects.

So, import everything but your data tables into a new MDB (or ACCDB,
for that matter), and create table links to your original MDB. Then
you can delete everything but the tables in your DM and synch with
all your replicas. Then you can distribute copies of the front end
MDB/ACCDB to all your users.

Since all the users are on the same LAN, you really don't need
replication at all, so far as I can see. All you need is to store
the back end MDB in a central location on a file server accessible
to all, and have the front end linked tables point to that shared
back end. This the standard setup for multiuser Access applications
and always has been.

In short, you really don't need replication at all. The purpose of
Jet replication is to be able to edit a single dataset in multiple
locations and be able to merge the edits through synchronization.
You don't have multiple locations, so you don't need replication.

Instructions on how to unreplicate are found in question 10 of my
Jet Replication Wiki FAQ:

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

And, of course, if I've completely misinterpreted your post and made
incorrect assumptions, I apologize. Please clarify and I'll be glad
to follow up to try to answer your questions.

I DON'T WANT ANY PASSWORD PROTECTION
join mdw from vba code
Different passwords in Access 2007
No more double-click code access?
Allowing people to only enter data into a form
Read only message
Extra DBs created
Remove or disassociate a mdw
Next Release of MS Access
password recovery for MS Access DB