Hmm... I don't know how well thought-out this product is. Consider the following scenario:

- VFP database containing a table with current/next PK values.
- Two sites, with fairly heavy data entry.
- Sync interval of 5 minutes.

At the start of the test, the sync process is run and databases at both sites are identical. Both sites start entering new records. At the end of 5 minutes each site has 10 new records. The records are completely different but have the same PK values.

BTW I forgot to mention that each record has 2 child line item records in another table. DBC triggers are not used (i.e. programmatic RI) and foreign key field names are not the same as the parent pkey field name.

I don't see how any sync program could resolve this. It probably isn't too hard to devise a scenario where even an expert developer working interactively couldn't sync the changes.

Bear in mind that "no changes are required to your program". Oh, read the fine print and "one field may need to be added to some tables". Can we say, "Software Warranty Null and Void"? Actually it sounds like it might incorporate FoxAudit or something like that. A transaction log would make life easier for syncing but still may not be a general "silver bullet".

Not to mention, there's a certain class of VFP apps that run "single-user" mode with SET EXCLUSIVE ON... < beg >