Tracking Undeclared Variables with FoxPro

Simon Arnold explains valuable uses for the LanguageOptions property : Tracking Undeclared Variables with FoxPro

This is similar to what the FoxMasters CodeInspector does , although their interface is a little easier to walkthrough than going through the text file.

The problem I have with the LanguageOptions is that you have to RUN your application – whereas with CodeInspector , you can do a scan right on the fly of your existing code.

Of course, if you tested each piece of code as you were writing it (a la FoxUnit methodology), the LanguageOptions approach would likely suffice but realistically for $79 US, CodeInspector would be a pretty good investment for any developer/manager who has to review other people’s code.