Sorry Scott, but this is absolutely not a bug, but actually it's more like a FIXED bug. VFP has always required fixed length index keys, but earlier versions were forgiving, which could either result in wrong results, or even cause crash, I have seen it happen. Now you can set ansi off if you want to live dangerously, or you can change the index key to give fixed lengths, and live safely. It's your decision...

By the way, it's too sad that MS gives you a totally wrong answer.

>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. 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"