Hi Sergey,
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...
>>Oh, I see. Should closing the file (as we did, in the tests) flush the Windows cache?
>
>No it doesn't
>
>> And, is there a way to disable the Windows cache? Or is FLUSH FORCE the only option here?
>
>There's Win API that allows to flush Windows buffers FlushFileBuffers
http://msdn2.microsoft.com/en-us/library/aa364439.aspx
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
