Hi!

The buffers I meant are not the buffers used for different buffering modes for tables. These are internal VFP memory buffers used to cache data for best performance. Even after tableupdate() there could be left something in memory not written to disk immediately. FLUSH will assre content of these buffers written to disks completely.

Yes sys(1104) could help, as well as suggestion from Sergey. Just test with first, second or both.



>>>In a Web environment, I have 4 VFP servers running to process the incoming requests. I have found that occasionnaly, one save by a VFP server is not reflected immediately on another VFP server. What I mean by that is that it may takes up to two seconds before the other servers can read the updated data from the tables.
>>>
>>>It seems that I have to force a flush here.
>>>
>>>What would be the best approach to make sure all data is saved on disk immediately after the VFP server that did the save transaction?
>>
>>FLUSH force buffers to save, it is recommended to use it after transaction that contain new records into VFP tables. SYS(1104) might help also, but usually to assure buffers contain the latest information. Maybe data for another server buffered for certain time so it des not see changes for 2 seconds using cached information. Try SYS(1104) to refresh buffers immediately without waiting for SET REFRESH settings work.
>>This also could be a network caching issue, but I do not know exactly.
>
>We do not use buffering.
>
>SET REFRESH is set to default as we didn't change it. So, it should be 0.
>
>It is not a network issue as those 4 servers are running on the data server.
>
>In such environment, are we forced to use SYS(1104) in order to avoid such problem?