>Can you give us a bit more info Steve?... Like

The table has the following structure:
1 CLAIMNO Character 10
2 BATCHNO Character 12
3 INVNO Character 12
4 ID Character 7
5 PROG Character 1
6 COC Character 5
7 DOS Date 8
8 DOBILL Date 8
9 VCODE Character 6
10 PROVCODE Character 9
11 PROVLIC Character 9
12 TOTCHARGE Numeric 8 2
13 TOTPAID Numeric 8 2
14 SERVCODE Character 3
15 SPECCODE Character 3
16 DRG Character 3
17 DODISCH Date 8
18 DAYS Numeric 3 0
19 DIAG1 Character 6
20 PROC1 Character 5
21 USERID Character 10
22 USERDATE Date 8
23 GLACCTNO Character 12
24 CHKREQNO Character 8
25 PAYMETH Character 1
26 PAYCODE Character 2
27 AUTHNO Character 10
28 DENYDATE Date 8
29 REFERNO Character 10


>
>1) What is the complete index expression?

claimno

>
>2) What network software is in use?

We have NT network

>
>3) How many concurrent users?

10-15

>4) Is this in a 'production' CDX or an ancillary one?

production

>5) The version of FP/VFP in use.

VFP 3.0

>6) Anything else you think might be helpful.

Every night the table is being zapped, appended and reindexed, but that doesnt help

>
>Jim N
>
>>I have an application which is heavily used on a network. The app is built around a table with 150,000+ records, and about 800 new records added every day.
>>The table has 16 indexes in the cdx, and the primary index gets screwed up every day. What happens is that by the end of the day about 10 out of 800 records are missing (meaning if I set order to my primary index, they are not found, but all other indexes find them).
>>Just for curiosity I added another index, same as my primary, and watched it for 3 days: this index is updated properly, nothing is missing, while my primary got screwed up again... I thought the problem is because of overuse, but I'm not sure.
>>Does anybody knows how to deal with it?