Jon,
I don't know how I'd do that at runtime. I'm responsible for final code reviews for a large VFP team. I've found it helpful to write VFP code that parses out the code and checks various things. [variable naming, scope definition, comments, etc.] I do this just before a "build." You could check then for the DODEFAULT()s that you are looking for. I've found the easiest way to pull the code out of the ??x tables is to use the _SCCTEXT program. DO (_SCCTEXT) WITH "MyForm.scx", then parse the resultant text file.

I hope this helps. Good luck with your QA endeavors.

Marty

>I find it difficult to understand why you question a design you know nothing about. The only reason we are trying to do this is as a developer aid. This is a large project that consists of many forms and controls that are sub-classed by a number of levels. For the framework to operate successfully it is required that developers put DODEFAULT code in certain methods - and we felt it would aid the QA process to issue a warning at runtime if this code was omitted.
>
>Jon.