>COuld be a corrupted index. Also, you might want to add a FLUSH after your TABLEUPDATE()

Hi, Craig.

I'm practically certain the problem is not in the table itself. I can remove the table from the DBC, copy it to an ascii file (deli), delete the table, rebuild it with CREATE, reload the data, readd the table in the DBC, and the problem comes back. I think this process eliminates any possibility of a currupted index.

In at least one case it is related to the data in the table because if I skip the reload step above and add records to an empty table, then I don't see the problem. But I can also load that same ascii data to an identical table with a different name and I don't see the problem.

On Toni Feltman's recommedation I added a FLUSH after the TABLEUPDATE() in CDataBehavior.saverecord() and this had no effect on the problem.

When I copied one of my problem tables to a new project and built everything up from scratch (new DBC) I did not see the problem. I'm thinking the key here is the new DBC. I'm about to rebuild the DBC in my main project. (Readd the tables, default values, etc.)

Thanks for thinking about this.

Peter