>Hi,
>
>I believe it has something to do with buffering. The behaviour you described is Record Buffering.
>
>Hope to help.
>
>Dennis

No... apparently with ADO, data will commit as soon as you move the record pointer. The only way to stop that behavior is to start a transaction right away. Then you can manually commit when you want to. This goes against what I learned about foxpro transactions which are supposed to be kept as short as possible.

begin transaction
if tableupdate 
    end transaction
else
    rollback

So with ADO I have to start a transaction then edit one or more records keeping the transaction open the whole time, then commit the changes when I am done.

Apparently ADO.Net doesn't work that way but I haven't tried it.