Michelle,

The problem with not "finding" the index is a classic problem of not having enough file handles. Here's what happens:

1. Let's say your file handles limit is 40 (I think that's Netware's default)
2. You have 39 files open and attempt to open myfile.dbf which has myfile.cdx associated with it.
3. FoxPro opens myfile.dbf, but can't open the cdx because there are no more file handles. You would expect an error message, but FoxPro just happily opens the dbf and goes on as if nothing is wrong.
4. You shut everything down and do it again and it works because there aren't as many files open when you get to the point where you open myfile.dbf.

Hope this helps,

Josh


>>It sounds like their indexes are getting corrupted. Make sure you have a reindex routine that deletes all the indexes and re-creates them from scratch.
>
>We wen 'round and 'round with this when I posted about the index problem. There's nothing wrong with the index, it just sometimes doesn't find it. For example, there's an index that puts the billing reports in order of their paysource. She ran it once and they were all out of order. She ran it again and they were in order.
>
>
>>Also, if their sever or workstations crash frequently that could cause the problem.
>
>As far as I know they don't have a problem with frequent crashes.
>
>>Also, it could be a problem with not enough file handles. If they're using Netware they may need to set the Netware FILE HANDLES= setting. I'm not sure how to do this under Win '95 (in DOS you just put a FILE HANDLES= line in the NET.CFG), but someone could probably help you with that.
>
>I'll ask their IS department about this.
>
>Thanks,