We had a design master (DM7), that was being synched every morning at
12:15am. This kept the design master from expiring, and also allowed
design
changes to apply to the "hub" while activity was low. As field users
synched their replicas, they got the new design changes. This has worked
well for us for the last year.
Last week, we had to create a new design master (DM8) as design changes in
DM7 were no longer updating to the hub. All went well creating the new
design master. I now notice in our transaction log (homebuilt, reading
the
Access system tables) that we are getting an automatic synch attempt every
15 minutes. Nothing transfers because it can't find the replicata (DM7).
Replica Manager no longer shows DM7, so I can't change the schedule from
there. On the 'hub" database, where DM7 was synching to, I can see the
schedule entry in the MSYSSchedule table. It won't let me change or
delete
the entry for DM7, to keep it from attempting to synch.
It seems to me that when I dropped DM7 from the replica set (using Replica
Manager), that it should have deleted any schedule items for the replica
as
well. It seems to have done this in the past (I have disabled synch
schedules in the Schedule table).
This probably would not be an issue if I had deleted the schedule (while
it
still was visible in Replication Manager) prior to removing the the
defunct
replica. But that time is past. How do I remove the schedule entry or
keep
the defunt replica from attempting to synch.
Thanks in advance,
Don
|
