>even easier:
>
>In the property window in the method tab a method which is interpreted as overloaded will be shown as such, only the inherited methods will be listed in non bold but cursive text. That way you have an overview and a place where you can check, if the method is working as inherited or not.
>
>You might find out how VFP determines this and then could write a script to check for methods regarded as overloaded but still being empty. Make that as a project hook in the beforebuild event and you get a compiler warning.
It's quite possible to write a builder which would check for pemstatus() of any methods (to see if they are changed), or to use amembers() filtered for changed methods. Either way, just like in the PEM window, it takes a human eye to decide whether a one-liner method is there by intent or by accident.