That was what I originally thought, but the new form seemed to open and get the old information before the changes were committed with the tableupdate which did work. I had controls bound to the table and they would be the old values, but the datasession browse would show the new values. I could a command button on the new form to refresh and all was okay. However, it was not a solution. I finally did put the tableupdate in a method which I called from the click event of the button callling the new form and this seemed to correct the problem. However, I am still confused as why I experienced my orginal problem.

Thanks for the reply

>Ronald,
>
>Do you check for the return value when issuing TABLEUPDATE()? In case TABLEUPDATE fails, changes to your data will not be saved; so you still have the old values.
>
>HTH,
>Dennis
>
>
>>I have been experiencing irregular results.
>>
>>I have a form where a command button will call another form. Since I am using buffering (5), in the click event of the command button, a tableupdate is called and the form called has it's own private datasession. However, the new form called will sometimes have the committed changes and othertimes will have the old values.
>>
>>Is the antivirus software a factor here? Is there a way to wait until the tableupdate has been finished before calling the new form?