Synchronisation problems

[Madhup Thakur]

WinXP, Access2003 and Access 2007

There are two ver of Access i.e ver 2003 and 2007 in a set of PC's running a
database. The master copy of the DB is on ver 2007 and replicas on A2007 /
A2003. The problem that I am facing is that when I change the structure of
tables /form the DB does not synchronise with message stating to the effect
that the change in the structure could not be applied to the replicas.
Basically the changes that I make has to do with autonumber fields in table
replacing it number fields and some minor modication in forms structure. Any
help would be greatly appreciated. TIA.

Regards,

Madhup Thakur

 

[Tom van Stiphout]

On Thu, 24 Jul 2008 18:36:32 +0530, "Madhup Thakur"

Replication was not designed to be used to replicate design changes.
So don't use it for that purpose. "It worked before" is not a good
reason to continue this practice.
Next to workgroup security, replication is an advanced topic you
should thoroughly study before embarking upon.

-Tom.
Microsoft Access MVP

 

[Madhup Thakur]

Thanks Tom,

Your insight to my problem is categorical, However I was under the
impression that on the master of the replica one could effect the design
changes.
BTW do you have a solution beyond synchronising all the DB and then creating
a new replica set???

Thank you for you time
Madhup Thakur

 

[boblarson]

Only data should be replicated. The backend (table design changes will occur
naturally if replicated). Forms and other objects should just be modified in
the frontend (this should be a split frontend/backend) and the users get a
new copy of the frontend.

See here for more on replication:
http://www.dfenton.com/DFA/Replication/index.php?title=Main_Page

--
Bob Larson
Access MVP
Access World Forums Administrator
Utter Access VIP

Tutorials at http://www.btabdevelopment.com

__________________________________

 

[David W. Fenton]

On Thu, 24 Jul 2008 18:36:32 +0530, "Madhup Thakur"

Replication was not designed to be used to replicate design
changes.

That's patently false. It works just fine for design changes to pure
Jet objects.

But changes to data structures require careful planning because in
any one synch operation, design changes are applied before updates,
regardless of the order in which those changes were made in the
Design Master.

So, if you're changing referential integrity (or any fields involved
in them) or validation rules, you want to make the data conform to
the new rules, synch the whole replica set, and only *then* apply
the structural changes.

So don't use it for that purpose. "It worked before" is not a good
reason to continue this practice.
Next to workgroup security, replication is an advanced topic you
should thoroughly study before embarking upon.

While replication should not be used for front-end objects (and it
sounds to me like the original poster has an unsplit database),
there is nothing wrong with propagating design changes to your back
end.

 

[David W. Fenton]

Only data should be replicated. The backend (table design changes
will occur naturally if replicated). Forms and other objects
should just be modified in the frontend (this should be a split
frontend/backend) and the users get a new copy of the frontend.

This is correct.

Replicated apps should always be split, just as any non-replicated
multi-user app should be.