>I guess it is apples and oranges, but my IS department wants to move to an Intranet even for local apps with the idea of eliminating work station run times. My argument is that even .NET requires a run time and we should continue with VFP for local apps (instead of converting to .NET).
>


Disclaimer: In advance, I was sorry for my poor English... :-)



You are mixing 2 diffenrent worlds on the same sentence: "move to an Intranet even for local apps".
If your app was on the intranet, it is no more local.

If your real concern was to continue to use Fox to build your apps,
you can consider converting (rewrite) most of them to web using a framework (like webconnection).
On this case you have to install the vfp runtime only on the web server.
Using this approach, you are in line with the IS dept pov that dont want to install
local apps and runtimes on workstations.

But you cannot compete against a web app only armed with your local vfp application
on the front of the ease of deployement... The .NET runtime need to be only on the server
and the vfp runtime need to be installed (or at least accesible) on each workstation.
For hundreds of PC, this is an real headake for the IT dept.

My last 5 years of vfp dev was mostly for web applications on intranet sites.
I have build some really complex applications that was used by a lot of peoples.
A couple of months ago I went to a client to install a new version of its app.
I take a look a the log, nothing was logged: the app run non stop since my
last visit 5 months earlier and have take thousands of hits by days!

My main "sales pitch" point was the ease of deployment:
all you need on the workstation, and its was allready there, is a browser.


To conclude, if your concern was to continue with VFP, learn a web framework.
Otherwise, learn .NET :-)

HTH