(snip)
>I agree with this wish only for LOCAL (CLIENT) data. There IS a way (as far as I know) to tell OS to do not buffer or cache certain files, locally.
>
>Jim, I think you should re-phrase this wish to make it more clear. FLUSH should control caching only for LOCAL computer, where it have control and power to do so. It should not do this for any other kind of storage, because no controlling on the way that storage manages cache and writes.
>
>Please, improve your wish.
>
>If it is only about SERVER - I also would vote against it, because, TECHNICALLY, I see it useless and very hard to implement.
>

Vlad,

I'm in total agreement. Speaking for myself, it was understood that the issue is about the local machine. Client/Server and other networked cases are obviously another matter altogether - a red herring in the context of this wish. Let's not forget that VFP is also a tool for building standalone applications that run locally. The wish, for me, is that FLUSH do what it says in the documentation, what it used to do before things got "advanced". Totally disabling write-caching is rather heavy-handed, and it would be nice not to burden VFP programmers with the intricasies of Window API and version dependencies in such a basic operation.

Mike