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 ===== Original Message from [EMAIL PROTECTED] at 9/26/01 7:06 pm >Running RB6.5++ DOS using a WIN2000 server, WIN2000 Pro sp2 workstations > >I have a program that APPENDS data from an invoicing table to an accounting >table when each batch of invoices are finished processing. 9 columns of the >41 column invoicing table are appended to the 45 column accounting table. > >Everything works fine, most of the time. However, every so often, it fails >to append with a message about "I/O problem...check for full disk..." with a >reference to a problem updating the indexes. The disk is not full (I have >gotten the full disk message a million times over the last 20 years and the >disk has Never been full). The problem is one or more of the indexes on the >accounting table is corrupted. The accounting table has 10 indexes, one on >an autonum column and one on a computed column (which contains some indexed >and some not-indexed columns). All the indexes are single column indexes. > >The only way I have been able to "fix" this is to run a program that drops >all the indexes on the accounting table and then recreate them. After this >is done, the append works fine. I also tried using insert instead of append >with the same results. (I use append so I don't have to specify columns). >I can't seem to discover which index(es) on the table is/are the problem and >if it is the same index(es). How could one determine this? > >Anyways, what could cause the indexes to get corrupted? There are only a >few people using the accounting table. This indexing problem never happens >in any of the other 50 tables (out of 350) containing 188 indexes that is >used by everyone and which have data appended to them or inserted into them >all the time. > >This was a problem about 6 months ago, then it went away and now it has >appeared 4 times in the last 2 weeks (both before & after the last reload). >I don't think anything relating to the accounting table has changed >recently. > >I have the "fix" programs but I would like to not have to keep fixing it. >Also, I have STATICDB set ON so I have to wait until I am the only user so I >can set staticdb off and drop/create the indexes. This problem also appears >when I had STATICDB set OFF. > >Any thoughts? > >Frank Radice >[EMAIL PROTECTED]
