I unreplicated my database but i still have residual tables for the
replication process.  Is there a way to clear them???
Regards,
Eddie

I downloaded and ran the TSI Unreplicator on an Access 2003 database. It
seemed to work. However, I still can't delete the replication fields in the
tables (e.g. s_GUID). I also downloaded the sysfld40.exe utility but can't
seem to make it work. For example, I enter

I'm looking for a check list which would allow me to reference as I write a
proposal to migrate to AD 2003 and Exchange 2003.  Is there something like
this out there?
Thank you in advance

Has anyone ever seen a situation where a user generates conflicts with
himself?  I've been working with Jet replication for years and have never
seen such a thing.  This only seems to occur where the user (and not all
users) first enters a new record, synchs with the hub, then ...

I occasionally find that some records which have been modified are not
being synchronized.
To fix the problem we basically re-edit the offending records and
re-synch.

I've followed the instructions for Setting Up Indirect replication for
Access 2003 Jet 4 SP8 all patches and service packs on 2 Win2k Machines
patched to the hilt. With TSI and all that happens is that I get is a new
file which is my mdb backend file name with a .sgn extension in ...

I know I'm barraging the newsgroup with questions but this
is all very foreign to me and I don't want to launch off into
development with a bad plan.
If two of my users are on laptops, what happens when my

In the Replication FAQ there are examples for code based synchronization
using both JRO and DAO. Which is prefered?
JRO
-----------------------------------------------------------

Let me begin by saying that I have searched Google, but I must not
be using the correct verbage, because I'm not finding what I need.
I have a client who, I believe, will benefit from replicating their new
Access database I'm building for them.  However, I'm inexperienced

If a child of a replica is disconnected from the network for
an extended period, say a week, it could be assumed that
when they reattach there will be a number of conflicts.  How
are they handled?

In the Replication FAQ it suggests compacting twice before
initiating synchronization.  Is this still the suggested practice?
Does it apply equally for data changes as it does for table
schema changes?

I just posted a question about Replication Manager, but I also
need advice about my decision to go with Replication in general.
I have a new client who want their Excel data moved to Access.
They have only 4-6 users of this data and a couple of them want