>
>- Person A edits a record, then saves changes. Person B retrieves the record, but doesn't see the changes.
>
>- Person A adds a new record. The insert code does a lookup in a table to get the next Primary Key, then increments the counter in the field. Person B then does the same thing. However, because the writes from person A are cached, person B gets the same key.

Craig,

While I can't give you details, I'm sure that write caching is designed to ALWAYS properly handle the situations you describe WHEN PROPERLY IMPLEMENTED by the supporting software (including OSes and sub-components).
In the case you cite it could be the OS, it could be drivers or it could be VFP. VFP has a decent likelihood because of the multiplicity of settings that are implicated in this kind of thing and the fact that documentation about all of them (most especially how they relate/operate between each other) is sparse at best.

The other day you blamed ActiveX control vendors for making controls that don't work properly with VFP, saying they didn't obey all the rules as strictly as they should.
Since you believe that you should not have a problem believing this (which I can tell you is far more accurate than the ActiveX excuse).

JimN