I do lock the table & if the table won't lock, then someone has some type of lock (usually an edit lock) so it informs the user to have others in the dept to exit the table and then the user can try the program with the append operation again. It appears that the index problem exists BEFORE the append is attempted. Trying the append just reports that there is an indexing problem. As users, throughout the day add/edit rows in the accounting table, the indexes will get updated, thus, the indexes for this table (as well as many other tables) are in a constant state of flux.
I have indexes on computed columns in other tables that are accessed by everyone and haven't had problems with those tables. My questions again are: What can cause the corruption of the indexes on the table and how can I discover which index or indexes on the table are corrupted. -----Original Message----- From: Troy Sosamon [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 27, 2001 9:09 AM To: [EMAIL PROTECTED] Subject: RE: Index corruption Try putting a lock manual on the table before you do the append and then take it off. set lock tablename on append..... set lock tablename off Troy
