asked on

Remove replication fields from Access tables.

I have a .mdb file with a lot of tables. Some of the tables has replication fields, which I want to remove, because I want to upsize.
Replication was used long ago, but not anymore.
How can I remove the fields from my tables?
I know I can use a make table query, but there are many tables and I don't want to loose attributes of the fields.
I found a reference that seemed to solve the problem, but the links does not work anymore. The reference is
-
http://www.pcreview.co.uk/threads/how-to-remove-replication-fields.2641180/
-
I attach a database with two of the files.
-
Can you help me please?
Sapo_be.mdb

ASKER CERTIFIED SOLUTION

Jim Dettman (EE MVE)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Scott McDaniel (EE MVE )

Here's a MSFT article with all the steps outlined:

https://support.office.com/en-in/article/I-cannot-save-my-replicated-database-in-Access-2007-format-0d14cc8d-63f9-4ae6-8dea-d64c562a3ca5

Basically, you have to use MakeTable queries to move the data from your replicated tables to new un-replicated tables, and you have to be sure to NOT include any of the replication fields (the ones that start with "s_"). Creating new tables and importing the data will take care of that.

Note you also have to recreate the indexes and such for each of those tables.

If you have a LOT of tables this can be a daunting task, and one that can be prone to errors. Michael Kaplan (MichKa of Trigeminal Software) created a de-replicator, but unfortunately Michael is no longer with us (which is a very, very big loss to the Access world) and his site is down.

Fortunately Luke Chung at FMS is hosting a clone of that site (with permission, of course), and you can get it here:

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

This is the utility your link refers to.

Fritz Paul

ASKER

I got stuck with this. Finally with 0x80004005 Error. I will have to revisit the issue at a later stage. Probably later in December.
I believe Jim answered the basic question.
Thanks also to Scott.