I've done a few things like this before for documentation systems.

The best thing to do is to build your UI in HTML format from the start. Have some rendering objects that can handle HTML generation for all output. That way you can use the same code on each platform to generate the UI. For Web you pass the HTML back, for desktop you can run the Web Browser control or automate IE.

User input is a bit more tricky to make generic. If you present your UI as HTML you'll need different mechansims to read the user input - on the Web you'll use Request objects while on the client you probably use the browser's object model to retrieve input.

If your app is some sort of doc management system you might want to look at HTML Help Builder. Although it's a Help generation engine it also works well for all sorts of other document types using custom templates.

+++ Rick ---


>I'm writing an application that will need to be distributed on cd (it will be run from the cd with no internet connection on a min Pentium 1, 64Meg RAM machine). I also need it to run on intranets and from a website on the internet (as a thin client - browser only on client pc).
>
>I'd like to get feedback as to the best way to develop this system so that I won't have to duplicate code. Obviously there will be some significant differences between the deployments but I'd like to have as much of a centralized base of VFP code as I can. I'd like VFP as the back-end on the web server. The cd version will look like a web site (use HTML pages).
>
>Thanks for any thoughts!
>
>Sally