>But it is a bug, not trying to be argumentative here but it worked in VFP7 and 8 and re-writing 100s of selects in my app is not an option. Variable length keys are optimizable and have worked for me without any sketchy results for years.

Sure?

* run this into VFP9 ( 3 records ) or VFP7/8 ( 1 records )
CLEAR
CREATE CURSOR bugIndex (cc C(3))
INSERT INTO bugIndex VALUES ("")
INSERT INTO bugIndex VALUES ("A")
INSERT INTO bugIndex VALUES ("AA")
INDEX ON RTRIM(CC) TAG TTT
SET ANSI OFF
SELECT * FROM bugIndex WHERE RTRIM(CC)='AA'

>Bottom line is the VFP team in their haste to remain relevant and get funding from Bill and M$ needed to make VFP9 more ANSI-SQL compliant and tried to sneak one by us. "Well Mr. Developer, sorry you have to recode your app but WE think in our infinte wisdom you should be doing things our way"

This is normal, and I think that the same will happen with. NET.
The phone call to the MS shows what is clear,
very little they know what is correct and what is wrong.