Daniel Rail wrote:

> Hi,
>
> At August 27, 2004, 05:36, petesouthwest wrote:
>
> Then: thanks Andy, I had quiet stupidly
> > overlooked the situation you describe,

I did as well and learnt the hard way a long time ago in a former life
writing Paradox stuff, so you are not the only one.
And please do not be afraid to ask questions we all learn from each
other here, I certainly learn more than I help.

> I think date check field is a very good idea. Also, you'd probably
> need the original export file to compare with the actual database
> record to see if there was a change since the last export. And, if
> there was a change, which field(s) has changed, and does those fields
> match one or more fields of those changed by the user off-site. If you
> have some changed fields that match(between the off-site user's data
> and the server's), you'll need to do some conflict resolution,
> basically which change overrides the other. And that might have to be
> up to the end-user to decide, by showing them when the server data was
> changed and what is the newest data.

I agree with what Daniel says. And if it sounds like a lot of extra
work that you would rather not do take a look at the replication engines
out there as they will handle or help handle the conflict resolution.
Take a look too at IBLogManager as it might be able to help you.
If you have any more questions please ask.
Regards
Andy