>>>i may be thinking to myself here, but it's not easy to run VFP app on the. So, how do you tell your boss, who seems to be determined to running it on the internet, that it will takes a lot of work to make it work.
>
>>Now I'm confused. Your original question was how to make a desktop app LOOK like a web app, or so I thought. That would be a step backward, as it says somewhere on the Interface Hall Of Shame ( http://www.iarchitect.com/shame.htm ). The amount of work required to create an actual web interface is always significant, and depends on the extent to which your interface tier is separated from business rules and stuff. Rick says that on his website, and it applies no matter which tool you use.
>
>
>Sorry if I'm not making since right now. My boss want me to develop a call desk application that would take problem calls from user. He wants it look like a web page and later migrate it to the internet, hense, I'm just thinking to myself.

Actually,

You could do this by controlling the web browser through automation. All your I/O could be generated HTML which you display on the web server via automation. YOu can also use Web Connection to do this. This is basically how Rich Strahl does his HTML Help program... it uses the Web Browse control driven by a VFP program.

Of course, once you write all the logic of the program and the display logic to send HTML to the browser, it is not much futrhe to get it to work as a true web ap.

My suggestion though, if this isn't going to ship as a stand alone ap, the build it as a web application up front anyway. Run an IIS server on your lcan creating what is called and 'IntraNet'. Why the interium step?

BOb


BTW: Check out www.west-wind.com ... His article on Internet Enableing your VFP application is excellent, and I think it has a section on controlling the web browser, I know Rick's book does.