Re: Sync Failed; Record is Deleted -- Append Confusion

Tech-Archive recommends: Fix windows errors by optimizing your registry

mikej711 <mikej711@xxxxxxxxxxx> wrote in
news:542e3473-eeff-4acd-adc8-5d7d58a5dc64@xxxxxxxxxxxxxxxxxxxxxxxxxxx
:

I am new to replication and am confused - Even if the new replica
was an empty one (I've been to Mr Kaplan's page), wouldn't the
newly appended records, being just added, have a more recent
timestamp GUID then really warranted? Put another way, won't
appending the records overwrite the valuable timestamps we are
trying to preserve?

No, it doesn't matter. When you append, you're preserving the data
that matters to you and your application, and recreating new
replication data. Jet doesn't give a rat's ass about the contents of
the fields in your database. When you append problem records, you're
creating new replication data and that's all that matters to Jet.

I honestly don't understand why you think it would matter if it has
a new GUID, except if you think it will be synchronizing those
records with the existing records. It won't, of course. What you're
doing is deleting the old records, but preserving the data that
matters to you in the new records you create with the append.
Because they are new records, they will be appended and your data
will be preserved.

My client only has one split 2002 database an a LAN network (the
Design Master) and one field agent on a laptop, also split.

You're missing one replica -- the DM shouldn't be used as a regular
part of synchronizing. It should not be used for anything but making
changes to table designs. So, there should be a DM (kept somewhere
safe and synchronized only often enough to keep it from expiring)
and then you should have a shared replica on a server on the LAN
that is the one that gets used by users connected to the LAN, and is
the one the laptop users synch with.

I thought
I could handle this myself, but I'm overmatched in this. Sadly,
there is no replica farm and the DM has data in it (I've learned a
lot this past week).

Are you saying you can't synch between the DM and the laptop
replica? Try creating a new replica from the DM. That often "wakes
up" replication and synchronization works again.

Thanks for your help :>

PS You guys know a lot of stuff that isn't in your standard Access
book. Are there any books/sites you would recommend for learning
the TRUE ins and outs of replication?

I've been trying to create just such a site, the Jet Replication
Wiki:

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

Only one other person has actually contributed anything to it,
unfortunately (thought that contribution was of the highest
quality).

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.

Relevant Pages

  • Re: Bi-directional synchroniszation not working
    ... quickly compare before running the query as an append query, ... I just ran a test Append Query and tried to reinsert a record into ... cannot modify the replication system object 's_GUID' ... If the record does not exist in the target database, ...
    (microsoft.public.access.replication)
  • Re: Bi-directional synchroniszation not working
    ... The query failed with the message: ... You can't append any of the replication fields, ... If the record does not exist in the target database, ...
    (microsoft.public.access.replication)
  • cloneing?
    ... I have a merge replication that is really fouled up. ... Right now I have three offices working on the database ... append the data, ...
    (microsoft.public.sqlserver.replication)
  • Re: Merging data before replication
    ... But how can I append each database's data ... Paul Ibison SQL Server MVP, ... (recommended sql server 2000 replication book: ...
    (microsoft.public.sqlserver.replication)
  • Re: how to restart replication after a key violation failure is fi
    ... What I observed after a few minutes was that in the transaction dropdown ... Synchronizing" was grayed out and "Stop Synchronizing" appears to be active. ... How do I make the snapshot available? ... Looking for a SQL Server replication book? ...
    (microsoft.public.sqlserver.replication)