I would think that you would NOT want to convert the whole application to ASP, Cold Fusion, or even ASP.NET(C#/VB.NET) since this would be the most expensive, time consuming, and with uncertain results. The best bet might be to re-use your vfp app logic by encapsulating it in a vfp mtdll and calling it from ASP.NET or ASP. I would pick either option #3(check out ActiveVFP:http://www.activevfp.com/avfpdemo2) or Option #1(TS or Citrix)...

>After a couple of months of development of a VFP 8.0 property management desktop application a client wants to make it a web application such that apartment managers can log in remotely. After spending a bit of time doing some research I have come up with the following five options for the client:
>
>option 1 - keep current system but have users log in via Pcanywhere, Gotomypc, Citrix or TS
>option 2 - run vfp form locally on each user's pc but have the data on a central server - OLEDB
>option 3 - convert and run both vfp form and data over internet using ACTIVE DOCUMENT and/or 3rd party software - westwind, voodoo, etc,
>option 4 - convert VFP application to ASP, Cold Fusion or other web site language and run form and data over internet
>option 5 - go with web based 3rd party property management software
>
>There are tradeoffs with each of these but the the hard party is coming up with cost estimates for some of these scenarios. I have much experience with VFP locally and have built web sites using ASP, Cold Fusion, etc. but have never ported a VFP application to the web. I'm looking for any advice from others who may have gone down this path. Lastly let me add that the current application only has about 8 forms and the client has spent less than $5,000 so far. Also if you have an option 6 or 7, I would love to hear them.
>
>Thanks,
>
>Vim