That depends on the context. This will affect the order the records are displayed. Depending on the ROLLOVER clause of the SET CENTURY, 31/12/99 may be interpreted as 31/12/1999 or 31/12/2099. In the first case, all date passed 2000 will display before dates in 1900. In the second case, the order should be OK.

If this is compliant, that depends if the order affect the way the software operate.

BTW, if SET STRICTDATE = 2, I don't know if VFP will complain or not on the index, but if does, you will need to either modify the index or change the STRICTDATE to 1.

>I am converting a FoxPro2.6a app to VFPro6 on W95. Concerned
>to make it Year 2000 compliant I found an index in one of my
>FoxPro2.6a free tables containing:
>IIF(end_date=CTOD(" / / "),end_date,CTOD("31/12/99")- end_date)
>
>end_date is just a field in the table identifying a despatch date.
>I want to try to avoid restructuring/converting this table and I just
>wonder if I can just let it go on indexing negative numbers
>after the Year 2000. Or is this code really not compliant?
>Your help is much appreciated...