>>1. The new "Intellisense" seems to behave identically to the one in VB 5.0 - so close, in fact, I'm tempted to call VFP6.0 Visual FoxBasic 6.0. A VERY NICE feature.
>
>A retraction of this "feature". What the MS Team didn't tell the attendee's at the keynote where this "feature" was used is that ...
>
>They were using the VB5 class browser to browse VFP classes they were showing on the screen (without telling anyone at the time - which generated widespread criticism from beta testers and speakers in the know).
>
>This is good and bad news. Good in that VB5's browser can browse VFP classes, but bad in that the syntax helper is not functional. SuperCls is still needed.
>
>
>Sorry about the misinformation on "Intellisense".

VB5's browser can browse VFP5 objects already and use them in intellisense, as long as they are compiled into ActiveX EXEs or ActiveX DLLs. However, VFP5 does not put all the required info into the type library that is needed (like parameters that should be passed and the types of values expected.) Until this is done, where VFP's browser can read all COM objects properly and use intellisense (and VFP itself compiles COM objects properly), I don't think anyone else (meaning non-VFP developers) would want to use VFP outside of us die-hards. VFP has to play fully in the COM arena to be taken seriously as a middle-tier product. I love VFP, but it has to work well with other tools.