Hi Charlie,

Not sure, I understood the whole your idea, some code sample would be helpful.
Currently we're using this syntax to update our tables
IF !TABLEUPDATE(2,.F.,ALIAS(),latuerror) etc.

I think, your solution would probably slow down the process, if I have 1,2 mln. records and made changes in 700000 records...

Anyway, I solved the problem by using the direct table changes instead of buffering, if the number of records greater than 10000. It's a little dangerous, but I don't have to make the users waiting 30-40 min... This job would be only run by single user, so it's not a multi-user problem...

Thanks again.

>If your using table buffering you could first isolate the changed records using getnextmodified(), then loop through them issuing the appropriate insert, update or delete SQL statement. For updates and deletes, key on the primary field. For inserts, check for the existance of a primary key.
>
>Charlie