>>Getting spoiled, aren't we? :)
>
>H"BackSpace"Well, I guess I was born that way. Endurance came later (probably helped by a stubborn streak).
>
>More on the point: which situations do you need to check ? If you are working with vfp sources the only thing to check for would be missing/forgotten local declarations, as all global/private vars should be intentional. If also scope naming rules were adhered to, chances for damage from once forgotten local should be minimal, as other locals are protected by *their* local definition.

Right - and I'm using the version of the tool by (Frank?) Dietrich, with the script attached to alt+6, that's quite enough for me, because 99% of my methods fit one screen, so a visual check suffices.

>If you are working on legacy FPx code, the problem is to decide which private variables should be considered "local" and wich variables are *used* as privates further up the calling stack. So it is helpful if at least the "usual" calling paths are covered, without macros and similar methods.

True, that's a nightmare to do manually. That's where a really powerful tool would be needed.