> In VFP 7, go to the Tools menu ... check box labeled "Enable Intellisense". Make sure that box is unchecked and then click OK. That will shut off intellisense for you.

if type("_VFP.LanguageOptions") <> "U"
   _VFP.LanguageOptions = 1
   _VFP.EditorOptions = ""
endif

in your personal config.fpw "COMMAND =" proggy does the same job if you routinely use multiple configurations. Unfortunately some VFP commands like the class browser reset the LanguageOptions - they had to ship VFP7 rather faster than they would have liked, it seems - so you have to keep setting LanguageOptions to 1 if you want it that way. Pity that this option does not generate errors anymore like it did in the beta. That was a really cool feature but now you have to analyze the debug output ... :-/

As regards DLL hell: when I tried to install VFP7 on a German NT 4 WKS I had to patch the OS to kingdom come (including some registry hacking) before the setup - or rather the blasted "Windows Component Update" - would let me install VFP7. The manual copy method (MSVCR70.DLL, VFP7R.DLL, VFP7R(ENU|DEU).DLL) worked fine for both IDE and compiled apps on NT 4 WKS and NT5 WKS at current patch levels, without any other updates (128-bit encryption would be required for the _crypt classes I was told, but who needs that double trouble anyway?).