>Hi Mark
>
>Yes it was supposed to say that Form1 is opened on machine 2 at the same time as Machine 1.
>
>Basically, the record is inserted and Tableupdated in the click of one button on Form1. The other button on form1 launches form2 - which is clicked on the other machine. It is Machine 2 in Form 2 that cannot see the new record.
>
>If Form2 is made to share the datasession of Form1 then there is no problem. If you close both forms on machine 2 and launch them again the record appears. We don't want to have to tell users to log all the way out of a processing form before they can run the view option which collates all Invoices/Receipts for a client.
>
>Was that any clearer??? :)

Yes, thanks. This is most strange. I vaguely remember that VFP will take advantage of a table that is already open in another workarea/DS when opening that table again in another area/DS.

Do you get the same results using Optimistic table buffering? I say this because if most of the activity is in inserting records, pessimistic buffering is not really necessary and optimistic buffering is usually the preferred method.

Have you eliminated the possibility of the server not writing the changes to disk in a timely manner? i.e., Have you tried waiting to open form2 on machine 2 to see if the inserts have been written to disk. If you have a machine 3, wait to open any forms until after machine 1 inserts records. Then go to machine 3 and open and close the forms until you see the new records. Then go to machine 2 which already has form1 open, and launche form2.

If machine 2 fails to see the new records, I would then say it is a problem with VFP reusing the data from the already opened table in form1.