Sylvain,

Turning your app into an ActiveDoc is very easy, you place the ActiveDoc class into your class library, place your startup in the Run event, and compile it as an app file. You do need to watch for several things:

1) As mentioned, the runtimes must be installed on the users machine. The easiest way to accomplish this is to create a simple web page that your users access, this web page automatically downloads and installs the runtime if needed. We use it and it works very well.

2) Data Access requires one of three methods. Either local access to the data, similar to how native VFP works, an internet mapped drive (LMHOSTS), or ODBC via SQL Server (the most preferred method). If your users are going to be using the internet, SQL Server is nice. A LMHOSTS mapped drive works, but of course with ANY internet application, data transport takes most of the time.

The advantages of ActiveDoc's is that the users can use the IE browser, which they are comfortable with, but don't have to work in a kludgy HTML document.

The only real-world alternative to ActiveDoc is Active Server Pages (ASP). But you still have data access issues (your users must download the appropriate ODBC drivers or Data Access Drivers and install them).

In Summary,
You users have to download Data Access, or the VFP run-time.

BTW, there is a knowledge base article on how to set up the web page to detect and automatically run the VFP runtime download.