I disagree here... Having read Ed's posts on this topic, it is clear he lacks a basic understanding of both what Tx's are, and how they are implemented in VFP...

Here is one sentence:

<
Let say, we have cmdSave.click code that writes changes to three tables (one parent and two childs) and it's required to provide that changes will be really written to all tables, even if something will happen dow the road (e.g you wrote changes to the first child and then found parent record locked). In case you described (static), it's not job for transaction, it's really buffering (standard or simulated) task.
<

In fact, making sure data is written to ALL tables successfully is exactly what Tx's are for. To say that it is not a job for Tx's, and that buffering will solve the problem is flat out incorrect.




>Ed,
>
>Disregard my previous reply, I went back and reread Nancy's message and now I understand what you are saying. You are correct.