>Hi Rob, thanks for responding; this is exactly what happened :
>I had one table with around 250,000 records, let's say, in my case
>"Traffic cases" and "Domestic cases". I copied the table to
>a different location, with copy j:\data\*.* f:\data\ now I have two identical tables, table A and Table B, I deleted from table A the "Traffic cases" records
>and from table b I deleted the "Domestic cases"; NO PACK USED; now I have one table with just "Traffic Cases" and another one with just "Domestic cases".
>Fine right ?, well after 4 or 5 days the users started getting "Record is out of
>range" when they were trying to find records using the SEEK command.
>Well, at this point you know the index is corrupted, so I deleted all the
>TAGS, created the indexes from scratch and them began my nightmare.
>Users started calling because they could not find certain records. I looked into
>into a child table of that one and guess what ?, I have around 10,000 orphan records, that means I lost 10,000 records somewhere, scary huh !!?
>
>If you have read until here, you deserve a big THANKS, just for that.
>
>>I noticed no one had responded, so here's my try...
>>
>>My guess has to do with the deleted records and the setting of DELETED = ON or OFF. If you had DELETED ON and used VFP to copy/move the data to 'different place' (ie: USE xxx/COPY TO yyy), only the non-deleted records would be copied into the new table/location. Wouldn't that be what was desired when deleting records? Or are you just trying to 'hide' them? Are you sure the index was really corrupted and if so, how did you establish that fact? What do you mean by 'lost 10,000 records' -- is the record count now 10,000 less, or was a 'COUNT' operation showing 10k less than expected?
>>
>>HTH
>>
>>Rob

Hi Luis:

Yeah, sounds pretty bizarre. Dumb question: Are these two master tables and the (one ?) child table all in a DBC? Did you do anything with the child table(s)? Seems that the child might also want to be split up? Remember, the DBC contains pathing info, so maybe your application is still referring to the original tables -- or did you move them back into the original directories? Using DOS copy on tables in a DBC is probably not the best way to go, I think... Maybe links have been broken in the DBC. Have you updated the DBC for the new relations(and split-up files), using the database designer or code -- or not?

If none of the above applies or leads to the answer, then maybe you should consider hardware or network problems. Other than that, I'm out of guesses at this point...

HTH

Rob