Al,

In a scenario where FP2.5 code is running under VFP8 and the only technique used to prevent multi-user collisions is to occasionally set a lock on a record being edited in the form. No transactions, no buffering except for whatever is default, no nothing. Totally optimistic approach.
Well, in the days when this was an ok way to use Foxpro, somebody found that write-behind caching should be turned off. Only we can't remember was there anything foxpro specific in the reasoning.
Now, as you say, the OSs are different, VFP is different, equipment is different.
Only code, unfortunately, is the same.
Do you know anything that still applyes to write-behind caching and the kind of programming style I described?

Thanks,
--Andrew