>In this case, I would minimize emphasizing VFP (although use it heavily!) and use it as a middle tier ASP.NET component. This way it seems like more of a mainstream MS solution...
>
>>>Which part is not scalable: web, data, vfp itself??
>>
>>Of course, in this situation again, the attacker doesn't justify his opinion and simply said that VFP should be gone.

A question an IT consultant should be asked:
Have you ever assayed an installation and reported that "it works, there is no need to change anything."

From my government years, I can remember being hidden away with some EE's in an isolated parts cage and listening to them discuss the politics needed to allow a "favored" vendor to write a set of specifications so tight that only his company (the favored vendor's) could address all the issues on the bid.

Sometimes, to understand how a non-issue becomes an issue, we need look no further that some of the cubes in the IT/MIS ares:)