If you open another copy of the table in another VFP session (unbuffered noupdate), will you see the changes?

I think the actual changes may not be written to the disk.

>I'm not at all sure what you're asking for.
>
>I have a free table, which is filtered and displayed in a grid. At startup, buffering set to 5.
>
>User clicks on a record, then sees the fields from that record in a container. Everything else on the form outside of the container is now disabled. Eventually user must either click on "Save" or "Abort", which invoke TableUpdate and TableRevert respectively.
>
>As I mentioned, I get sporadic reports that a user changes a number of records, which are visible in the grid after clicking on "Save". The user then closes the form, comes back a while (hour or so) later and none of the changes stuck.
>
>>>The question remains ... if it failed, would the records where it failed appear in the grid as if they had not failed?
>>>
>>>No, that doesn't make sense to me at all.
>>>
>>>>>No, I haven't .. but suppose it did. Would the changed records appear in the grid if the update failed? If so, that seems counter-intuitive.
>>>>>
>>>>>BTW, what reasons might there be for an update failing? I do set the "Force" parameter to .T., FWIW
>>>>>
>>>>>>Do you check TableUpdate(1 ...) return value to make sure that it didn't fail?
>>>>>>
>>>>
>>>>Could be various reasons, you never know why this would fail - always need to code defensively.
>>
>>How exactly your interface is set up?