Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Documenting?
Message
From
07/06/2001 08:16:13
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
 
 
To
06/06/2001 17:08:00
Chuck Tripi
University of Wisconsin - Milwaukee
Milwaukee, Wisconsin, United States
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00516060
Message ID:
00516231
Views:
12
This message has been marked as the solution to the initial question of the thread.
>I did a Tools, Wizards, Documenting. I thought it would print a whole buch of codes and documenting, but instead it makes some kind of "copy" of the project into another directory? I am not knowledgeable with that Documenting, can someone help me? I did the same thing for Access 97 at some time ago and it did printed about 200+ pages, that is what I need (really, my supervisor wants it).

Chuck,

I thought the same thing until I researched some... Below is text directly from the MSDN Help for Visual Foxpro regarding the Documenting Wizard. The ones you are most likely interested in have a LST extension and are in text format.

Regards, Renoir


Documenting Wizard: Step 5 – Select Reports

Allows you to specify the types of reports that the Documenting Wizard creates. (The reports are actually text files.) The wizard can produce the types of reports listed in the following table.

Report Type File Name Remarks

Action Diagram project .act Shows the hierarchical relations within your code. If you are not working with ASCII code page 1250 and ANSI code page 1252, see the directive "*# document ACTIONCHARS" in Customizing the Documenting Wizard.

Cross-Reference Xref.lst Lists all the user-defined symbols.

File Listing Files .lst Lists all the files in the project.

Source Code Listing project .lst Puts all formatted code in a single file.

Tree Diagram Tree.lst Shows the procedure calling tree.


The wizard also automatically creates the following files.

File Name Description
Files.dbf Table with a record for each file in the project.
Fdxref.dbf Table with a record for each instance of user symbols in the code.


Fdxref.dbf contains a field named Flag for identifying the keywords. The identifiers are the following.

Flag Description
B Base class
C Class name
D Defined PROC or FUNC (not method)
F Function call: myproc( ) or DO myproc
K Keyword
M Method definition
N Name of file
O Object
P Property of an object
R User symbol reference
V User symbols (variable) definition (PARA, PRIV, PUBL, DIME)
Previous
Reply
Map
View

Click here to load this message in the networking platform