>Vlad_Georg:
>
>Thanx for the feedback, what you are saying makes sense. If the performance will be the same, going the internet route is probaly a better idea because there are no hassels updating client software, cross platform compatibility, easier access ect. However, the downside is, it will be very difficult to recreate the existing user interface in a web browser.
>

You are right regarding the interface, but there may be a solution for you. Have a look at www.west-wind.com. Rick's webconnection has a possibility to show the VFP - Forms in the IE 4.x. I think you'll need the runtimes on each of the clients.
It also may be the right time to redesign the interface. With CSS, JavaScript and Java you can do a lot more then plain HTML. Have a close look to CSS, it's a really powerfull "extension" to HTML.

>Here is another thought. Since the datasource will be on the same machine as the web server, I might get better performance with a VFP backend. Data is only traveling from the datasource to the webserver. The bandwith issues go away! VFP is much faster than any SQL database when you don't have bandwith limitations. Right? What do you think about this?
>
Yeah. You're certainly right, you will get better performance because of VFP as a backend and of the direct connection between database and webserver. The best solution would then be Rick's web connect, it's fast, written for VFP and has a lot of nice features. Have a look at his website, has ton's of infos. Also buy his book at www.hentzenwerke.com (it's not about his product, but about general vfp and internet development, even without thinking about vfp on the net it's worth the price). Another book for great ideas: "Philip and Alex's Guide to Web Publishing" by Philip Greenspun. It's Unix centric, but also tons of great ideas.

Have fun.