> you don't have to know pascal. you need to look at the way
> the replicator installs it's triggers and the tables it
> installs to manage the process. It uses PKs. It does not have
> to store the OLD and NEW values as you seem to be doing. It
> merely records the tablename and PK value of the record which
> has been inserted/updated/deleted. The replicator does the rest.
> Alan
>

Do you get much of a performance hit going back to the record to look for
changes, rather than having the changes in the log file ready?

My usage stats indicate only 1 or 2 fields are ever changed in a record -
meaning that storing the changes themselves probably wouldn't take up too
much space.

Just thrashing out alternatives...

N