Hi Jim,
Thnaks for the reply. I'm not sure I can do that though. A tableupdate / revert will write those changes to the tables correct?
FormA has a grid and edit button and OK/Cancel buttons. The grid shows 3 records in a paramaterised view. The user selects a row in the grid and clicks the edit button. I begin a transaction, show FormB that is editing a single row in FormA's view, the user makes changes and clicks OK, I end the transaction. Now the view has the changes, I can refresh the grid with the changes, and the user can still click cancel on FormA to dump the changes. If I used a tableupdate from FormB I would be writing those changes to table, which shouldn't happen until the user clicks the OK button on FormA.
Perhaps I'm misunderstanding something.
>Roi,
>
>No you don't need a transaction. Orient the edit form you can so when the user exits it that edit is eiahter committed or reverted. Use TableUpdate or TableRevert in the edit form to accomplish this.
Roi
'MCP' Visual FoxPro
In Rome, there was a poem.
About a dog, who found two bone.
He lick the one, he lick the other.
He went pyscho, he drop dead!