Hi Doug,

>
>Are you inserted records into the account balance table or just updating values? If the former, then this could be caused by table corruption, although you've used SDT to repair it so it shouldn't be an ongoing problem (unless corruption is recurring). If the latter, then check to ensure TABLEUPDATE() is returning .T. (I'm sure you're doing that, but JIC) and that you're not double-buffering the table (that is, the view is buffered *and* the table is buffered, so TABLEUPDATE() of the view is writing to the table's buffer, but you're not using TABLEUPDATE() on the table, so the changes are being discarded).
>

We are just updating fields on an existing record in the account balance table. We are using our framework's (ProMatrix) save routine to commit the data. As you might expect, it is a robust routine that will return various error codes for failures. It indicates success. I don't think we have any double-buffering going on, but I will double check we aren't manipulating the underlying table directly. As I said before, we close the view/table and re-open it, at which time it has the balance we expect. According to my logic, this indicates that at least VFP considers the data committed. Is that the conclusion you would make?

Thanks for the suggestions.