> "Nick" <nickmirro[ at ]spamarrest.com> wrote in
> news:ejuJHGo1GHA.4648[ at ]TK2MSFTNGP04.phx.gbl:
>
>> Our developer just added a couple of new tables to the back end
>> design master. This was done by copying the design master to an
>> ftp site, which he subsequently downloaded, worked on and then
>> re-uploaded to the ftp site. I then copied it back to the
>> original folder.
>
> You just cannot do this. Any replica (and the DM is just a special
> replica) as to remain in place to maintain its ReplicaID. Once it
> was moved and opened in the new location, it changed ReplicaID and
> then could not be the DM any longer.
>
>> Unfortunately, he sent back a replica (for a yet unknown reason)
>> instead of a design master. I initially missed that. When the
>> back end was finally in the original folder, I then synched with
>> one of the members of the rep set. The conflict message box
>> opened. Strange since no new data was entered in the interim by
>> any end user.
>
> Are there conflict tables?
>
>> Anyway, when I clicked 'yes' to resolve, the message box closed
>> and no conflict resolution window appeared. On compact and
>> reopen, the message box appears again but no window results when
>> 'yes' is clicked.
>>
>> Of note, after reopening the db - following the first conflict
>> message - the size jumped from 17.9 to 21.6 mb in that instant.
>
> You have done something illegal (moving a replica without using the
> MOVE REPLICA function in ReplMan, the TSI Synchronizer or JRO), and
> this creates "dead replicas." There is no predicting what kind of
> problems this will cause over time, and it may not be possible to
> correct the error (though I doubt it's unresolvable).
>
> --
> David W. Fenton
http://www.dfenton.com/> usenet at dfenton dot com
http://www.dfenton.com/DFA/