Hi!
You require to indentify records by some way. You cannot make exact rules for such updating. Add a field to the table wich is integer record unique ID number. This do not required to be shown in the interface or anywhere in the client application, just add it for internal purposes (replication).
>Hi,
> Thank you for your information.
> I think the main mistake in my application is, I re-use the PK. I don't have any unique integer used as PK, instead i am using value such as user entered customer ID as PK. And my app allow the deleted PK value to be re-used. for example:
>
>
>PK Delete Mark
>VIP01 .T.
>VIP02 .F.
>VIP01 .F.
>
>
>Therefore, it cause problem when comparing records between working and backup record. The record marked '*****' will be insertewd into my forward table either. Any ideas?
>
>Thank you
Vlad Grynchyshyn, Project Manager, MCP
vgryn@yahoo.comICQ #10709245
The professional level of programmer could be determined by level of stupidity of his/her bugs
It is not appropriate to say that question is "foolish". There could be only foolish answers. Everybody passed period of time when knows nothing about something.