>>>>>Are you surethat Machine A is doing a TABLEUPDATE()? Are you sure the TABLEUPDATE is successful
>>>>
>>>>Yes, Machine A is doing a successful TABLEUPDATE
>>>>
>>>>
>>>
>>>This kind of problem is difficult to diagnose inside a framework (didn't oyu mention you were using VMP?).
>>>
>>>Try opening the view froma commad window in a VFP session on both machines, making a change in one, TABLEUPDATEing it, and REQUERYing the otherto see if the data shows up. Basically reproduce what you think is happening in your program, but without the uncertainty of hidden code. Your results will tell you whether this is a view definition problem, a buffering problem, or a code problem.
>>
>>I'll give that a try. Thanks.
>>
>>Dan
>
>Ok. I opened 2 VFP sessions, and set up table buffering on both machines. I added one record to vfp session A. I then went to the vfp session B and did a requery. The record is not showing. I issued a FLUSH as was suggested by Barbara Peisch and this did not work either.
>
>I suspected that I was dealing with a VMP problem, and now it looks like it has to be a problem with the view itself.
>
>Dan
Ok. Next round of tests... If you close VFP session B, reopen it, and REQUERY(),does the data show up? What about if you TABLEUPDATE from A, and close session A? IOW, does the view update ever work? This will determine if it is a view definition, or a network buffering problem...
Erik Moore
Clientelligence