>Our Intellisense isn't VB's intellisense. It's not internal to the language, it's external. In fact, I *think* it's even written in VFP.

Umm, it is, and it isn't. Calvin had to do some internal work to get it going, and then xBase code was written to get the scripting and keyword expansion stuff working.

The key is that it's extensible, and some of the scripts that I have would blow you away. I mean, type "ado" in the VB shell and see if it doesn't produce code to go look for the latest build, install it, build your multi-threaded DLL, register it with MTS/COM+, then fire off a 72 hour stress run against the VFP OLE DB Provider.

Or it can make coffee; your choice.

Yes, I understand how the whole WITH...ENDWITH issue makes VFP pale in comparison to VB's command completion. We suck. :-)