>I have an application to support. Application was made with VFP 6.
>
>I have all the source code but no real docs with it.
>
>Where should I begin, to figure out the most out of that application?
>
>Is the documenting wizard in VFP enough?
>
>Is there something better with the documenting wizard in VFP7 (which I have) or VFP8 (Which I don't have yet)?
>
>Are there better tools out there for VFP that would help figure out the ins and outs of the source code?
>
>I guess that amongst the most important things to do is to find out where the fields for all the table are used?
>
>Any suggestions on things that I forgot to mention?

Yes, the table structures are very important. You should try to find out (and document) what is the purpose of each table, and of each field.

I would start by simply running the program, and figure out the user interface from the point of view of the user. Then, look at the source code, and try to find out how key pieces work.

Some specific questions I might ask are:

What are the main forms, and what tables do they use?

Does the program use OOP, classes, and such? For what purposes are classes used?

Did the original developer take advantage of a. a database container, b. buffering, b. triggers, etc. (try to think of some additional "modern technology")?

HTH,

Hilmar.

Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)