Hi Bruce,

I think your theory is probably right. I remember running into a similar situation using FoxPro 2.x when the user had the SMARTDRV cache on their machine. If the user crashed or sometimes even logged out quickly after closing the app the saved data would be missing from the tables.

This was because FoxPro was keeping an internal cache of the data and when shutting down the app the implicit FLUSH would put the data to the SMARTDRV level of the cache and may not make it from there to the network in time.

When we turned off write caching or removed it entirely the problem went away.

>I'm offering a theory here that would account for lost data I posted about this morning. There are 3 tables on the server. A user opens them up EXCL in an app, does an hour of edits, the machine crashes, and all the edits are lost. This is with table buffering, and in spite of constant Tableupdates during the editing. All tables have edit timestamps, and no stamps were made for the editing period. All tables are fine otherwise, the editing was re-done without trouble.
>
>The theory is that somehow the vfp app copied the entire tables (which are quite small) into local memory, and performed all the Tableupdates on the local copies. The the machine crashed, and the copies were never returned to the server.
>
>I realize this sounds odd, and I've never had anything like it before, but I can't account for the data loss in any other way.
>
>I would like to think this can't be true, but can anyone tell me that this theory is not possible?