dbTalk Databases Forums  

removing replicas from list-box (A2003)

comp.databases.ms-access comp.databases.ms-access


Discuss removing replicas from list-box (A2003) in the comp.databases.ms-access forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Cliff McLane
 
Posts: n/a

Default removing replicas from list-box (A2003) - 05-09-2011 , 04:52 AM






Hello, when I try to synchronize my local replica with a non existent
design master or an other non existent replica, an error message
appears to inform me about the missing database. Thereafter the
question comes up: if I want to remove the missing database from the
list. It doesn't matter if I answer yes or no the database stay in the
list. Now my question. is there a possibility to remove manually the
database names from the list? maybe in the registry?
tx 4 your help

Reply With Quote
  #2  
Old   
David-W-Fenton
 
Posts: n/a

Default Re: removing replicas from list-box (A2003) - 05-11-2011 , 07:20 PM






Cliff McLane <orionxvii (AT) gmail (DOT) com> wrote in
news:939872bd-698c-4f7c-8abb-e364117085aa (AT) p7g2000yqd (DOT) googlegroups.com
:

Quote:
Hello, when I try to synchronize my local replica with a non
existent design master or an other non existent replica, an error
message appears to inform me about the missing database.
Thereafter the question comes up: if I want to remove the missing
database from the list. It doesn't matter if I answer yes or no
the database stay in the list. Now my question. is there a
possibility to remove manually the database names from the list?
maybe in the registry?
No, the names of the replicas are stored in the replica itself, not
in the registry.

To remove a replica from a replica set, you have to synch with THE
ACTUAL LOCATION the replica was at. That is, if you had this
replica:

\\MyServer\Databases\Replica1.mdb

....you have to have \\MyServer\Databases\ available to you to synch
with.

Also, because of the vagaries of how the information on replicas is
stored (one listing of \\MyServer\Databases\Replica1.mdb might
actually represent more than one replica, particularly if you've
been abusing replication and creating "dead replicas," such that
multiple replicas with different ReplicaIDs had the same
filename/path), you may need to repeat this attempted synch several
times before the replica is no longer listed.

There is no easy way to do this. When I've cleaned up a replica set,
I used an old PC and changed its name and set up the appropriate
shares so I could synch with it as though it were the actual
computer listed in the dropdown. Then I changed the name of the PC
again and remapped shares appropriately repeatedly until I'd removed
all the dead replicas from the list.

If you've got any significant number of dead replicas, you (or
somebody) have been abusing Jet replication. You should never be
copying live replicas via the file system, unless they have never
been synched with another replica, and you're intending to create a
new replica in the process.

Details on all these issues at the Jet Replication Wiki:

http://dfenton.com/DFA/Replication/

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.