Way back machine= year(1992).ish
Microsoft networking corrupts VFP indexes.
Novell also hosed indexes using old client with an option called Opportunistic Locking (ie cached locks, or "locks held in memory").
Subsequent versions of Client32 dropped the client-side caching.
Too buggy.
Here is one OLD reference:
http://dbforums.com/arch/125/2002/10/528965MS networking doesnt do much write caching and the source has probably not changed much since 3COM 3Open/Lan Manager(IBM OS/2) days.
But the locking mechanism always sucked.
Because MS networking is not a real RPC-style (Novell speak = file opening closing locking and unlocking protocol) protocol.
I always flush, or tableupdate ,use , reopen on network apps anyways.
