>>>Issue the FLUSH after the TABLEUPDATE. However, FLUSH only writes the buffers on the PC, not on the network server. I strongly recommend that you turn off all the write cache on the server's disk controller.
>
>PMJI...
>
>I turned of the write cache on my NT server a few months ago becuase of some "lost delayed write" error occuring during nightly backups. I found the registry hack for disabling the cache on the MS web site.
>
>Everything worked fine until I wanted to copy some files from the Server to a shared folder on another coputer on the network. I got some error message about "semaphores", and the fix for this problem was to ENABLE the cache feature!
>
>So... I need the caching for file copies, but I don't need it for purposes of committing data input from a network workstation. How can I win?
>
>I too have had some data input from a network computer not get committed to the file server table on VFP5. When this happens, the last 10 or so records in the table are corrupt, and I have to re-index in order to fix the table, but the records are indeed lost.
>
>I recently learned about the FLUSH command, but you said it only works on table stored on the local machine, not the server. What do you recommend to force the server to write to this disk from a remote workstation?

I'm not aware of any way to force the server to flush its data buffers. My next suggestion is to make the write cache as small as possible.