Re: Replicas

From: Cheval (NoSpam.Ask_at_ForEmail.com)
Date: 02/09/05


Date: Wed, 09 Feb 2005 21:33:08 GMT

The undocumented first rule with Access Replication: Only Replicate Tables.
Split the database into two files any only replicate the backend (tables
only file). Copy the front end (Queries, Forms, Macros, Modules) to each
user.

One more thing, a little word of advice, don't let the users modify the
front end. Really! Give them a "play" front end of their own to use to their
desire.

In my systems I have two database front ends that they can open. The main
standard one for data maintenance, standard reports, etc and a personal play
one that sits in their home folder. The standard one checks for the latest
version of itself and downloads and opens it. The users personal play one
links to the same replicated backend file tables as the standard one so they
can do anything that want. eg, In the play database they can create
temporary and customised tables, queries, reports, etc. They can even import
a standard report form the main database front-end, customise it for their
personal needs and then even delete it from their play database again
without worrying about wrecking anything.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
"Jackie Reyes via AccessMonster.com" <forum@AccessMonster.com> wrote in
message news:767dd0ccd46c4b1abd8c1154c50d0bab@AccessMonster.com...
Hello,

I've replicated my database and realized that there may be some limitations
for the users of a Replica. I have made several reports, queries, and
macros in the Design Master and synchronized it to the replicas. However, I
noticed that in the Replica, a user can't make any kind of changes to any
of the reports. Is there a way to override this? I want to allow the users
the ability to make changes themselves.

-- 
Message posted via http://www.accessmonster.com


Relevant Pages

  • Re: Queries - Back Ends and Replication
    ... replicating the Forms and Reports. ... The backend should contain tables ONLY. ... It is not necessary to replicate in order to manage the user ... they reattatch to the database, ...
    (microsoft.public.access.tablesdbdesign)
  • Re: on-line and near-line databases
    ... 'B' database) and only keep users from the last 30 days in the ... data restoration approach. ... Copy the records in the subscriber database which are to be ... ready and we 'replicate the execution of the ...
    (microsoft.public.sqlserver.replication)
  • Re: Strange behavior of replicaset
    ... In other words I need to split the database? ... > You create what's called a front end application and replicate the back ... > The front end is a standard .mdb which holds queries, forms, reports, ...
    (microsoft.public.access.replication)
  • Re: Replication for Access
    ... I imported the tables, forms, queries, reports, and modules into and new ... database and regenerated the tables and links to create a new unreplicated ... When I try to replicate the data file it keeps saying the file is all ready ...
    (microsoft.public.access.replication)
  • Selective Replication
    ... Have two schemas in the same database. ... used for currents an A_HIST is used to capture ... Using Triggers on 20 tables in A to replicate ... and have flexibility of possibly have the A_HIST schema in a different ...
    (comp.databases.oracle.server)