>Back in the DOS days when I switched from Clipper 87 to 5.2, I turned on one of the compiler options that tossed up a warning if it found a variable un-declared. At first it was a real PITA to deal with, but eventually you found yourself writing much tighter code - the apps I put out were that much cleaner, ran faster and were easier to "grok" after a time. It would be nice if VFP had a compiler option or SET ABUSIVE ON setting that would force us to declare everything. That's one thing I truly miss...

Look up the help for _vfp.LanguageOptions. You already have this in VFP 7.

[addition, after having read the rest of the thread: this is just a tool to catch undeclared variables, and works for most of the cases - but not at compile time, and that's bad.]