Bob,
Are you testing the value of the BizObj.Save()? (One of the biggest mistakes we've made is assuming return values are good once we've done the initial SET STEP ON routine to test our code.)

If the TABLEUPDATE() fails, you won't necessarily get an "error," in the sense of a crash. I guess it depends on your definition of "error!"

The PK ID field being incremented is indicative solely of a new record being successfully added to the view in question.
It doesn't mean that the record is added (or committed) to the table.

Hope that helps,
---J

>Has anyone ever come across a problem when adding rows to a table through a standard MM business object and the index on the table has become corrupt?
>
>I have an audit table that records changes to other tables in the database. I use a standard business object to create a new row using the new method, I replace the column values accordingly and save the object using the save method.
>
>No errors take place, the id table gets incremented properly for the primary key id value, but no rows are added to the audit table. After dropping the index and recreating the index, the object works properly (until of course the index gets corrupted again.)
>
>This sounds like a VFP issue, however, it is very disconcerting, since no errors are being triggered and the rows that should have been inserted are lost.
>
>Any help in this is appreciated.