I just download it and opened it. “VisioModeler™ is a tool for designing databases, and for analyzing existing database structures. “
This is fine, a good tool to work with database, but what about the code?

Is there any tool or any approach that I should know to document an existing system?
I want to get first a general idea of how the system works. What tables are in use. what code is used, maybe there are tables or pieces of code that are not used.

In the perfect world a system will have a System Analysis with flowcharts and descriptions of all the pieces of code, forms and any other files, but what if you don't have anything and you have to Reverse engineer?


>>I remember something about that threat. Just did not remember the tool you mention. I'll take a look up for InfoModeler if I can find it.
>
>Go to www.microsoft.com, and search for "VisioModeler".
>
>I just found out about this recently, and didn't yet have the time to try it.
>
>>Framework yes, I've definitely thought about getting one, BUT, I am getting the system now and I am currently not using or have any experience with one. So I will have to spend time learning both framework and system.
>>And, what if the client wants to maintain the system themselves in the future since they have foxpro programmers in site and don’t necessarily own whatever framework I may purchase?
>
>If you use a framework, the client will have to have a license for it, just as the client has to have a license for VFP.
>
>Free frameworks are available, as well, which might still help you save some work.