Design Master Question

[leslieann47]

After replicating my database, the forms and reports in my design master now
show up as replicas and I am unable to create a new form, report, or macro.
Is it supposed to be this way? And if not, is there a way to fix it?

Thanks.

 

[leslieann47]

After replicating my database, the forms and reports in my design master now
show up as replicas and I am unable to create a new form, report, or macro.
Is it supposed to be this way? And if not, is there a way to fix it?

Thanks.

I answered my own question. What I thought was the design master was
actually a replica. I guess renamed the design master which is what might
have caused the problem. I have since just made a new design master. Thanks.

 

[David W. Fenton]

I answered my own question. What I thought was the design master
was actually a replica. I guess renamed the design master which
is what might have caused the problem. I have since just made a
new design master.

You also need to be aware that you shouldn't be replicating anything
but data tables, as Jet replication works reliably in the long run
only with pure Jet objects (which would be tables and queries).

Your app should be split, into an unreplicated front end with your
forms/reports/etc. and a replicated back end with nothing but your
data tables. Failure to do that can lead to corruption of your VBA
project and the complete loss of all your forms/reports/etc. It can
also put your replica in a state that it can no longer synch with
other replicas.

Replication is for data, not for anything else.

 

[John Spencer]

Moving the design master or renaming it will change the design master
into a replica.

'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

 

[David W. Fenton]

Moving the design master or renaming it will change the design
master into a replica.

And it will cause any non-DM replica to become a completely
different replica from the standpoint of Jet's internal replication
functionality.

In other words, it's not something you should ever do without using
the MoveReplica command (available only in Replication Manager and
with the TSI Synchronizer -- the fact that it's not available in JRO
just shows how worthless JRO is).