Changing a replica to a Design Master

G

Guest

I created a design master and synched with the replica in order to make
changes in reports at the design master while others were using the replica.
BUT, have since been advised that this is dangerous and that I should split
the database. I am not sure that this is necessary in our situation and
would just like to return my database to the original unreplicated state so
that I can make edits to the forms. The Design master has lost relationships
(likely with the synching?) so I just want to return the replica to the
original "virgin" state and start over. Possible??? Would anyone advise me?
 
D

David W. Fenton

I created a design master and synched with the replica in order to
make changes in reports at the design master while others were
using the replica. BUT, have since been advised that this is
dangerous and that I should split the database. I am not sure
that this is necessary in our situation

IT IS ALWAYS NECESSARY.

Replication has nothing to do with the need to split -- you need to
split even in an unreplicated database.

But replication makes it even more urgent, because replication is
not friendly to front-end objects -- given enough time, you will
eventually corrupt your replica set and be unable to synch. You
could even lose the whole replica set if you're not careful.
and
would just like to return my database to the original unreplicated
state so that I can make edits to the forms.

All you have to do is import the non-table objects into a new
unreplicated MDB.
The Design master has lost relationships
(likely with the synching?) so I just want to return the replica
to the original "virgin" state and start over. Possible??? Would
anyone advise me?

If you've lost relational integrity, that indicates that you've
likely had a corrupt primary key index. This is likely due to the
lack of splitting, and the synchronization while a user was editing,
which has its dangers even when you're replicating only tables
(particularly with memo fields edited in bound forms).

If you want to unreplicate the tables, pointers can be found on my
Jet Replication Wiki FAQ page:

http://dfenton.com/DFA/Replication/index.php?title=FAQ

See question 10 at the end.

I don't know anything about unreplicating front end objects, since
I've never replicated any (since I have never created an unsplit
Access application, so never replicated anything but tables), but I
do know that if you import them into an unreplicated MDB, they are
not longer replicated. --
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
 
G

Guest

Thank you very much for your wisdom...I was able to UN-replicate my database
with success for most of it and am just working on cleaning up a few things.
Thanks again!
Cheese
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top