Ok Thanks. I use Flush Force and had forgotten that it was a wrapper around FlushFileBuffers. Somehow I thought FlushFileBufers was something totally different... Just me being dense again :o)


>You would use FlushFileBuffers to make sure that data is actually written to the disk. It's up to you to decide when and how often you want to do that. The more often you do that the less posibility of corruption tables on the disk but you'll pay for that in performance. Check Re: NT Buffer Flush? Message #647125 for sample code.
>
>In VFP9 you can use FLUSH FORCE which is a wrapper around FlushFileBuffers .
>
>>Is this a fix to a seek offset error or entirely different? I can't picture how this would work in a typical scenario. Let's say I use queries from SQLServer for managing some data, and additionally I have a couple of local dbf tables that remain open throughout the life of the app. How would I get the handle of a table when I open it up initially so that I could use FlushFileBuffers to write the data in the buffers? Am I not understanding and its purpose is entirely different? I guess I'm not clear on when using FlushFileBuffers api is appropriate...
>>