>i browse that occasionally when my clients ask for dos-type stuff (why don't i have to use the function keys anymore???). funny how often m$ gets mentioned there.
>
>however, since most of my clients can use the common net browsers, but have (some) problems using anything else windows-based, running an app through a browser seems (to me) like a good idea. if vfp6 makes that easier, i'm all for it.
>
>< soapbox=off >

I'm all for the new web-friendly extensions to VFP. This will make my life as developing internal corporate apps alot easier. We are moving to almost exclusively web-based applications. The code runs on the server or automatically downloads to the client. I don't have to fly all over the country to install the software and any time we release updates, the users automatically get them the next time they connect to the web site. Also, we have Mac and Unix users in addition to the Windows majority. My web-based apps just require a browser which runs on any of the platforms. I don't have to create seperate apps with different installation requirements, etc.

We are doing alot of employee self-service type of development. This allows employees to update their own information, get training via the web (even at home). We also have alot of teaming sites where project teams can easily share files among, keep track of schedules and tasks, etc. All of the project information is in one common place where the entire team can always access the same information.

In my opinion, web-based applications offer all of the benefits of client/server application without the drawbacks. Of course, there are drawbacks to this technology as well. This is where VFP can really help. Using IE and VFP technology combined with a web server you can implement applications that are very close in functionality to standalone Windows apps.