We sell a multiuser application written in VFP6.0. It has been just recently that we have been distributing it to customers who are running it on Windows 2000. We are having problems where it appears that a seek or locate fail on a recently added record in the same instance that added it. An engineer at Microsoft has told me he believes it to be a caching problem specific to Windows 2000.

When a record is added it is added to cache memory and FoxPro tells the OS to flush the cache at the apropriate times but the OS believes it is smarter and decides to wait. When we come along later to search for it using the seek command, the CDX file has not been updated and the seek fails. It doesn't make scense to me that the seek would read directly from the file and not from the cache but who I am I to argue with the engineer.

I have searched the archives and found many posts concerning other problems with corrupted memo files, forms and reports that people have attributed to a caching problem. I don't know if anyone has looked at the totality of the evindence to link all these to a problem with the Win 2000 cache manager.

I find the whole caching concept disturbing when it comes to a multiuser application. If one PC has records in cache for even short periods of time, how can any other PC trust that that it is able to access all of the available records or the most recent edits? I also find it disturbing that the Engineer is recomending a third party utility that forces the cache manager to flush the cache to disk. Why can't Microsoft just fix the problem. The whole thing is sounding fishy. I am suspecting they know there is a problem but enough peaple are not catching it and complaining so they are not devoting the resources to fix it.

If you have experienced a problem that sounds like it may be caused by the same thing let me know how or if you fixed it. If enough people band together we should be able to get it resolved.