>Ed,
>
>I will have to disagree with you here. I've used Transaction management and it works. I think you have to have buffering on, I know you have to have a .dbc.
>
>I BEGIN TRANSACTION at save time, and raise a ROLLBACK if anything goes wrong. I rely on the RLOCK/UNLOCK (with somewhat less succes since today, see my thread about unloc) to prevent simultaneous updates.
>
>Feels good to post positive :). Should try this more often.
>
>Marc
>
>
Marc,

I agree that you need the dbc, which is there and I have a transaction class that is handling that job. Like you, it does a rollback if an error occurs. I've found it to work without buffering on the tables though. I can only say that I know this because if an error happens, the updates do not take place. I have not done rigorous testing of it.

Steve