Heya Craig -
ya - Active Documents were not the way to go, but he did mention version 6, and the word 'Form' was stuck in there. I'll let it slide that speaking of Active Documents is a bad idea - I tried to give a caveat, subliminally of course.

I was hoping he'd change his concept of 'using the form on the web server', but his spec was rather bare [so far].

He could, of course, keep the vfp front end at the client side and use a web server as a data store for his VFP data.
http://www.gnsinfotech.com/Articles/a_simple_way_to_make_your_vfp_de.htm

This can be massaged a bit as well, and make any other backend data store work in the same fashion.

In a stronger, active voice:
Active Documents are not the way to go with Visual FoxPro 6. Don't drink that koolaid.

Moises, as is, you can't get there from here [ Active Doc equal-ing your 'FORM' is a bad idea]. OTOH, AFP is a great tool for slinging data and rendering the html you need , programmable in an asp-like fashion with native non-visual VFP code in the older asp style pages.
I uploaded a doc file here on it some time past, but why not look at the new beastie ? You can run AFP inside of apache these days (as well as IIS), so you have LOTS of options.

mondo regards [Bill]

>IMO, Bill gives some good and bad advice. There are good VFP-based solutions, and some others. You can also use .NET and get to the data through OLEDB. But, you won't be able to use your VFP form on the web. ActiveDoc is not a good solution. There's a reason that Microsoft backed off Active Docs. They have big security holes.
>
>
>>I have a table and a form in my desktop
>>
>>I would link to install VFP 6.0 in my website to run
>>this form and the table only to add and search
>>clients etc...
>>Is it possible ? Which toold do I need
>>
>>TIA
>>
>>Moises