>Maybe someone can help me with a database problem I'm working on. Here is scenario: every time my form is run and the user adds a record to the table MEQU and two corresponding child tables MEQPTENGHST and MEQPTTRANS, the index file for table MEQU is corrupted. The result is, that as long as an order is set on the MEQU table, the record, which was just added, cannot be seen. Has anyone ever run across corrupt index files, and if so, how did you resolve the problem?

Aleks Bulgakov had a scenario few months ago, where it happened. The solution was to keep the offended table alread open AGAIN in another work area under some other alias or in a different datasession (at least his example stopped misbehaving when I did that) - see thread "Index and transaction", thread #116702, 14th of July.