You could:
1.) keep your vfp app as is and run it thru a browser via MS Terminal Server. Maybe only a short-term solution.
2.) Use vfp web services - there will be your desktop app and it will call methods from a central web server over the internet.
3.) Convert your GUI screens to HTML or use some sort of tool to re-use the screens and keep your VFP logic in VFP mtdll components. This is similar to web services but will return HTML as output.
4.) Convert to .NET web forms - will give an approximation of desktop capabilities on the web, but, will involve a major conversion.
5.) Combination of #3 and #4.
>This may be a basic 'stupid question', but here goes:
>
>I've been developing VFP desktop apps for years. Lots of really cool apps with really involved UI's/business logic etc. The apps are currently in VFP8 (back end data and all).
>
>Now my users are hearing 'intranet' and wanting to move everything to browser based apps.
>
>This is my question. My clients seem to think that *every* app is better off running on the web. I am thinking that some of these apps can't run on the web because the UI is too involved and complicated. Am I missing something? I've never seen an interactive web site that does field level validation and many of the other great vfp features.
>
>There is no such thing as 'converting' a vfp desk top app to web is there? It's a total rewrite no matter what language I use. Is that correct?
>
>thanks
>
>bonnie