All I can say, is that I don't "like" the index expression you show us, since VFP actually has to add two values and see if the sum is empty. If any of these fields are editable, VFP will check this index tag for integrity reasons quite often, I believe. Why not change the expression into something "easier". I don't know how you use this index. If you Set Order to this index, your options are somewhat limited, but they exist. However, if it's for filtering, I suggest separate index tags for wireout, start_time and finish_time.

Another thing I observe, is that the field name Finish_time is more than 10 characters, so this table must be a member of a dbc. Could that be problematic? I really don't know.

>I have an issue with CDX files. Please see Screen-Shots.
>
>- Screen-Shot #1 - The fields in question are Date fields Due_Date1 and Due_Date2.
>- Screen Shot #2 - No Index is based on these 2 fields. They are based on two other Text fields Start_Time and Finish_TIme.
>- Screen Shot #3 - As you can see Due_Date1 and Due_Date2 are bound to 2 Date Spinners control on Order Entry form..
>
>The problem is 3-4 times out of 10, when they increase or decrease the Due date spinners, they get the error:
>"Error # 114: Index does not match"
>
>This is really not a real error where the index file are actually damaged. They are not.
>It's just a bogus error that goes away, when the form is closed and reopened..
>The table and it's index file are just fine. It's only after the Date is changed that the error is triggered. All is fine afterwards.
>
>I can try to capture this error at some point in the flow, and throw it away, but I would rather fix it.
>Any ideas why this is happening?
>
>Thanks.