You might be correct..The indexes used were only for Temporary Indexes on Views for Reports, etc...it's possible the data was such that no problems occured. I wasn't even aware of any issues until testing with VFP9.


>The indexes were likely corrupted, I wouldn't call this "worked".
>
>Thanks,
>Aleksey.
>
>>Hi Aleksey,
>>
>>Actually they've worked in apps going back to version 5.
>>
>>Marshal
>>
>>>Hi Marshal,
>>>
>>>>Indexes with Variable Length components which worked on all previous versions now generate an error.
>>>>
>>>
>>>The error indicates the opposite, they didn't work in previous versions.
>>>
>>>Thanks,
>>>Aleksey.
>>>
>>>
>>>>I have just begun to test some of my existing apps with VFP9 and have noticed the same behavior...Indexes with Variable Length components which worked on all previous versions now generate an error. Apparently VFP9 is much less forgiving than previous versions.
>>>>
>>>>>Hi Ronald,
>>>>>
>>>>>>ALLTRIM(STR(add_type))+DTOC(startd8)+ALLTRIM(STR(fk_patients))
>>>>>>
>>>>>
>>>>>This is improper key expression. DTOC(startd8) behaves differently depending on the current SET CENTURY and SET DATE, you should use DTOC(startd8,1) instead.
>>>>>
>>>>>Thanks,
>>>>>Aleksey.
>>>>>
>>>>>
>>>>>
>>>>>>The following index in VFP9.0 beta worked fine when doing an insert into the table:
>>>>>>
>>>>>>
>>>>>>ALLTRIM(STR(add_type))+DTOC(startd8)+ALLTRIM(STR(fk_patients))
>>>>>>
>>>>>>where add_type is an integer field,
>>>>>>startd8 is a date field,
>>>>>>and fk_patients is an integer
>>>>>>
>>>>>>Today, I finally downloaded released VFP9.0 and am getting the following error:
>>>>>>
>>>>>>"Error building key for Index ..."
>>>>>>
>>>>>>Removal of index program runs fine and then adding index back in seems to work.
>>>>>>
>>>>>>Can anyone give me a hint as to why the above index is giving me trouble?
>>>>>>
>>>>>>Thanks in advance