How to convert a replica back to a normal database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I would like to know ways to convert a replicated database (the replica or
the design master) back to a normal database.

Thanks,
em
 
This will help:

http://support.microsoft.com/kb/282977/en-us
Click to expand...

These links will help more:

* Access 2002 instructions (should work for A2003, too)

http://support.microsoft.com/kb/290052/

* Access 2000 instructions

http://support.microsoft.com/kb/208394/

* Access 97 instructions

http://support.microsoft.com/kb/153526/

The A97 article also has a download link for the Jet 3.5
unreplication wizard:

http://support.microsoft.com/kb/168398/

There are two other tools that also work for Jet 4 databases:

* Michael Kaplan's TSI Un-Replicator Add-in

http://www.trigeminal.com/lang/1033/utility.asp?ItemID=7#7

* Graham Search's Unreplicate Utility

http://www.pacificdb.com.au/MVP/Code/UnReplicate.htm

The latter has code, and you could perhaps learn something by
reviewing the code, but I've never actually used the latter (I've
hardly ever unreplicated anything).
 
David W. Fenton said:
These links will help more:

* Access 2002 instructions (should work for A2003, too)

http://support.microsoft.com/kb/290052/

* Access 2000 instructions

http://support.microsoft.com/kb/208394/

* Access 97 instructions

http://support.microsoft.com/kb/153526/

The A97 article also has a download link for the Jet 3.5
unreplication wizard:

http://support.microsoft.com/kb/168398/

There are two other tools that also work for Jet 4 databases:

* Michael Kaplan's TSI Un-Replicator Add-in

http://www.trigeminal.com/lang/1033/utility.asp?ItemID=7#7

* Graham Search's Unreplicate Utility

http://www.pacificdb.com.au/MVP/Code/UnReplicate.htm

The latter has code, and you could perhaps learn something by
reviewing the code, but I've never actually used the latter (I've
hardly ever unreplicated anything).
Click to expand...

Thank you for the information.

I think the solution...exporting the objects to a clean database and
re-establishing the relationship is not a very efficient method when working
with a lot of table objects.

I haven't try the tools yet but I would like to know if the tool(s) can
perform the job in one step / more efficient?

EM
 
I think the solution...exporting the objects to a clean database
and re-establishing the relationship is not a very efficient
method when working with a lot of table objects.

I haven't try the tools yet but I would like to know if the
tool(s) can perform the job in one step / more efficient?
Click to expand...

For A97, the wizard would do all this for you. There has never been
a wizard for that after A97 from MS, but the tools listed at the
bottom may do it all for you.

The key issue is that importing the old tables into a non-replicated
database keeps the replication fields, which cannot be deleted
because, even though the table is no longer replicated, those are
considered system fields by Access/Jet and are not
editable/deletable.
 
Back
Top