Hi Joel.

>We have a client that is losing data in one table. The problem is associated with a payment reversal routine. We have one table that maintains a customer's account balance, and other tables that are affected by the reversal. The routine adjusts all these tables and commits the data inside a transaction (we are using local views). Later, the client finds that all tables have been committed properly, except for the one containing the account balance. There are other fields in the table beside the balance that aren't being updated, so we apparently are losing changes to the entire record. Of course, this behavior isn't consistent. The changes are saved successfully sometimes, and other times not.

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).

Doug