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.