Replication

[Guest]

I've been working on a database for sometime (that someone else has
created...I'm just fixing the issues after that person left the company). The
database is set up to be replicated and has been working just fine for some
time. But quite a few changes have been made and now when I try to
synchronize the databases I get an error that reads:

"The history of design changes in the replica does not match the history in
the Design Master."

I've never worked with replication and I'm wonder where to look to resolve
this current issue.

Any suggestions??

Thank you
Jim

 

[John Spencer]

Replication works fairly well with data changes in the tables.
It doesn't work as well with design changes.

If you can, the database should be split into a front end / back end
configuration with no replication on the front end.

When I have made design changes to the backend (data tables only), I have
sychronized all the replicas and then created new replicas from the master
to distribute along with the new front end that will work with redesigned
tables.

"One confused underwriter"

 

[Keith Wilby]

"One confused underwriter"

I've been working on a database for sometime (that someone else has
created...I'm just fixing the issues after that person left the company).
The
database is set up to be replicated and has been working just fine for
some
time. But quite a few changes have been made and now when I try to
synchronize the databases I get an error that reads:

"The history of design changes in the replica does not match the history
in
the Design Master."

I've never worked with replication and I'm wonder where to look to resolve
this current issue.

Any suggestions??

Thank you
Jim

I've haven't worked with replication for a long time but I'm guessing that
the design changes were made on a replica and not the design master.
Replication is a bad thing IMO and to be avoided at all cost - do you have
an alternative?

Regards,
Keith.
www.keithwilby.com

 

[Guest]

Changes were made to the forms, which were apparently set up to be
replicated, not just the tables. Is there a way to fix that?

Jim

 

[John Spencer]

I don't know if there is a way to recover.

I would try posting to the Replication news group -
Microsoft.Public.Access.Replication.

I would
-- back up what I have
-- see if I could synchronize just the tables
-- create new replicas

Read the replication white paper on MS site thoroughly before doing any
changes to the databases.
For Jet 3.5 look at
http://support.microsoft.com/?id=164553 - replication white paper
http://support.microsoft.com/?id=182886 - replication FAQ

For Jet 4.0
http://support.microsoft.com/?id=190766 - white paper
http://support.microsoft.com/?id=282977 - FAQ

Also see
http://www.trigeminal.com - excellent replication site

http://support.microsoft.com/support/access/content/repl/replication.asp


"One confused underwriter"