First of all, I don't know how to transform your desktop application into a Active Document application. I just want to give my 2 cents about Active Document.

Since an Active Document require that all VFP runtime be installed on the user's machine, what advantage does it offer? What benefits the browser give to my application versus the desktop one? I don't see one. Active Document would be great if a VFP application could be hosted inside a browser on any platform without the need of the runtime files. But with the runtime files, I prefer deliver a desktop application.

Just my 0.02$

>I am very interested in learning about Active Documents. I need to make my application an Active Document application. So far, I have designed the app. as if it were a desktop solution.
>
>So, one of my prime concerns is if it is too late to make my application an Active Doc application.
>
>Do I have to start over? I have followed the steps to create an active document in my "special edition" Using Visual FoxPro 6.0 book, but have not been successful.
>
>I understand that I need to create a class of the _active doc base class and set that new class, whatever I decide to name it, as the MAIN. I also understand how to accomplish that. I simply have to open up the foundation classes and drag the _active doc base class to the project, and a form pops up for me to name the new class. Then, I can drill down in my library hierarchy and set the new class to MAIN.
>
>My big concerns are how do I handle my tables and forms which already exist. Do I have to create each form over, based on a new class?
>
>
>If anyone has created an Active Document, I would sure like to hear your experiences and how you converted your existing forms and tables to be Active Documnet ready/compliant, so that the app. can be used in a browser.