>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

Thank you very much for that Marty. I wasn't aware of the _SCCTEXT program - this will be extremely useful to us.

However, being able to parse code at runtime would still be extremely useful for a couple of reasons :-

- It would mean developers correct problems before passing to code to review.

- At runtime it is possible to use ACLASS() to determine the entire class hierarchy. I.e, certain code may only be required in forms/controls that have certain ancestors.

Any more ideas on this would be greatly appreciated.

Once again, many thanks.
Jon.