>>>>I knew there got to be a reason why I stay with VFP 6 <g>.
>>>
>>>You don't know what you're missing. :) Intellisense itself is well worth upgrading.
>>
>>I agree with you 100% about usefulness of intellisense. And I often load VFP 7 to lookup a syntax using intellisense. I just don't have the confidence that VFP 7/8 is more stable than VFP 6 and therefore still maintain my customers' applications in VFP 6. Actually I was about to jump into VFP 8 when I discovered that bug mskb #Q190496 was not fixed in 7 and 8. This bug broke a lot of my code, where I had to jump through hoops to get around it. And I was looking forward to removing my "work-arounds" after upgrading to VFP 8 when I was really surprised that the bug is still there.
>
>What prevents you from doing coding in VFP7 and debugging and testing in VFP6? :) I worked this way for a while until we moved to VFP7/8.
>
>BTW, if MS KB says, "We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available", it means that no fix should be expected. :)

I hope you are kidding (at least that is how I understand your ":)"). Because if they don't fix this problem and the problem discovered by Igor in this thread, they won't see my money :-).

As far as testing and debugging. I am happy if I have time to test for my own bugs. I certainly don't have time to test for VFP bugs.