>>Thanks Jim,
>>And over the week end I was just exploring the buffrering modes of VFP. and came to find our that the FORM has a buffering fucntion and so does the cursor. Curcors have 4 buffering options which is pess. row buffer, pess table buff, opt row burr and opt table buff. While the FORM's has only two options which are pessimistic and optimistic buffering.
>>
>>Must both form and curcors bufferring be the same? and which will overwrite which when the form is run?
>>
>>Jeff
>>
>>>>Thanks,....but when do I issue TABLEUPDATE() and TAABLEREVERT()?...should I put them the the 'click' event of the command >buttons that I created for save and delete?
>>>Jeff,
>>>
>>>Yes that would be an ideal place for them. Better yet would be to give your fomr a SaveData Method and a RevertData method and put the TableUpdate() in teh SaveData and the TableRevert() in the revertData method. Have the click of your save button say;
>>>
>>> THISFORM.SaveData()
>>>
>>>The Cancel button could say;
>>>
>>> THISFORM.RevertData()
>>>
>>>This way the butotns never change no matter what form you use them in. You kust make sure the form has those two methods and that the needed code is in there.
>
>Table buffermode overrides form buffermode. If you use row buffering do not always thrust on a savedata(), revertdata() button thinking you could revert all session. In row buffering when the record pointer moves an implicit update occurs (ie: in a grid). Also take a look at begin transaction....end transaction (or rollback).
>Cetin


Thx but how do you use a transaction in a OOP environment,...which button should I create to do that?

Jeff