Replication and Local Tables

[wendyp]

I have a replicating database with 10 tables. Two of these tables are local. I have now discovered that I really need 1 other table to be local.

MSDN has an article about making a table local after the fact:

http://msdn.microsoft.com/library/d...s/office97/html/replicatingpartofdatabase.asp

The problem is that they say to do this BEFORE making the replica the design master. Ok, I got a replica and then realized, I can't create any modules or anything to run the code to set the table to local because it's NOT the design master.

Does anyone have any experience with this?

/Wendy

 

[MoLaker]

I'm going to make a suggestion you may not want to hear. It's only a matter of time, from my experience with MS JET replication, that you will have to rebuild your replicas. Something sometime, somewhere will get corrupted or too many conflicts will occur, or something. So, I recommend you address your problem by recreating your replicas with the new changes to the design master. Make sure all record updates have been replicated and conflicts resolved then go for it. You are going to need the practice.