Thanks, Mike. I learned of this from the Wiki and thought it was what I was looking for. However, after seeing this and Part 7, it looks like AStackInfo() is what I really needed.

Thanks.

>AProcInfo() is a design time tool that you can use to gather all the information about a program. There was a thread, while back, on how to gather all the Procedures in a PRG. In VFP7, you can do:
>
>AProcInfo(aProcs, 'mycommand.PRG')
>
>And that will create an array with all the Define #DEFINE preprocessor directives, Other preprocessor directives (such as #IF), Class definition lines or Procedures. The type of the element is defined in the third column if the third parameter is 0 (defaut) or 3. Also included in the array with the element name and type are the line numbers where they occur and the indentation.
>
>In the version I have, I don't think that the Indent is working properly (I get 0 for all of them). The third parameter accepts 0 - 3. 0 is all the info, 1 is just the class definitions (a parentclass column is included in this case), 2 includes just the class methods and events, and 3 lists only the pre-processor directives.
>
>I suppose since this is the same vein, there is also a new Document window, which will basically show you the outline of a PRG while you're editing, presumably using APRocInfo(). It lists all the Procs, Classes #Defines, and other #s. When you click on fucntion in the Doc Window, the PRG automatically moves to it. And the opposite, when you arrow up or down past elements, the Document window keeps in synch. Right clicking on the window allows you to sort the list by name, location or type, and hide certain types.