Not sure what you're talking about - vfp can continue to be used as web applications and be accessed by a web browser alone. It's this type of comment and Whil Hentzen's in InfoWeek that are damaging to the perception of VFP, in my opinion...
>Hi,
>
>This morning I had to hear yet another reason why everybody should migrate to dotNET.
>
>Deployment.
>
>Deployment? Yes! There is a new corporate decision in one of my clients that no software (i.e. applications) should be installed in a user's PC.
>
>I argued that *all* my applications don't reside in user's PCs and that there is no install routines whatsoever in order for a user to use *any* of my applications (all .exe reside in specific server's directories, and .ini files and dbfs as well). All that should be done is to create a shortcut in user's PC desktop to start the program and, if that's the case, configure an ODBC connection if the app needs to access an SQL backend. Aha!!! so you *must* install something in a user's PC!
>
>I also presented the WTS option. NO! All should be done via "web" access (i.e. using a browser) and *all* apps should be web applications, accessed by and running under a browser, and... it should be developed in dotNET!
>
>That's all.
>
>Thanks for your time reading this message
>
>Fernando