Replication problem

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Neil L - 28 Sep 2005 16:46 GMT

i have a database which need to share, problem is when i create a replica the
master copy stops working so i cant change any design features,

the backend is on a network share, with the front end replica on a different
computer

Any ideas whats causing this??

thanks Neil

Reply to this Message

David W. Fenton - 28 Sep 2005 20:31 GMT

> i have a database which need to share, problem is when i create a
> replica the master copy stops working so i cant change any design
> features,

Does the copy you're calling the "master copy" say "DESIGN MASTER"
in the database window's title bar when you open it? If not, then
it's not the DM, and you need to find the DM to make changes.

> the backend is on a network share, with the front end replica on a
> different computer
>
> Any ideas whats causing this??

The only thing that would make sense is if you moved the design
master after replicating it -- that demotes it from DM status and
makes it a regular replica. You can fix that by opening the one that
*should* be the DM and choosing RECOVER DESIGN MASTER on the
Replication menu.

But the main point:

Do not under any circumstnces ever move replicas. Once a replica is
created, it *must* remain in its original location. It can only be
moved with the Replication Manager's MOVE REPLICA functionality (it
can also be done programatically with the TSI Synchronizer).

Signature

David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

Reply to this Message

Neil L - 30 Sep 2005 13:05 GMT

Hi David,

The copy is the design master but it crashes when i try to open it, the
replica works fine but when i changed it to the design master that crashed
as well, the database works fine until i create a replica

when i open the design master i get either an error saying invalid data
format, on debuging it says that its the variables i have, but these work
fine in the database before its replicated or it crashes and gives you the
menu saying access has encounted a problem etc

any ideas

thanks Neil

>> i have a database which need to share, problem is when i create a
>> replica the master copy stops working so i cant change any design
[quoted text clipped - 21 lines]
>moved with the Replication Manager's MOVE REPLICA functionality (it
>can also be done programatically with the TSI Synchronizer).

Reply to this Message

David W. Fenton - 30 Sep 2005 21:44 GMT

> The copy is the design master but it crashes when i try to open
> it, the replica works fine but when i changed it to the design
[quoted text clipped - 6 lines]
> crashes and gives you the menu saying access has encounted a
> problem etc

Do you have forms and reports in your replicated database? If so,
that's likely the problem. Replication really works only for tables
and queries -- replicating anything else is a crapshoot that often
ends up corrupted and unusable.

Signature

David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

Reply to this Message

Neil L - 07 Oct 2005 12:10 GMT

is there any other way of sharing a database with forms reports etc which
wont crash the database

thanks Neil

>> The copy is the design master but it crashes when i try to open
>> it, the replica works fine but when i changed it to the design
[quoted text clipped - 6 lines]
>and queries -- replicating anything else is a crapshoot that often
>ends up corrupted and unusable.

Reply to this Message

David W. Fenton - 07 Oct 2005 21:22 GMT

>>> The copy is the design master but it crashes when i try to open
>>> it, the replica works fine but when i changed it to the design
[quoted text clipped - 9 lines]
> is there any other way of sharing a database with forms reports
> etc which wont crash the database

First off, there is one basic thing about *all* Access applications
that for some reason many people never seem to realize:

The application should be split into two parts:

1. an MDB with just the data tables. One copy of this is on your
server and shared by everyone. This is called the BACK END.

2. an MDB with the forms, reports, macros and modules that is linked
to the tables in the data MDB. All users should have their own
copies, so that no front end is opened by more than one user at a
time. This is called the FRONT END.

Since there's no data in the front end, to give a user a new one, it
just has to be copied to their computer, over to of the old one.
This can be done manually in Windows Explorer, by executing a batch
file, or by using a utility like the one created by Tony Toews for
automatically distributing front end updates (see
http://www.granite.ab.ca/access/autofe.htm).

I've used all three methods in different circumstances and it's no
big deal at all.

Signature

David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

Reply to this Message