>>> 1. Maturity.
>2. Reliability.
>3. Flexibility.
>4. A proven track record.
>5. Lack of "The Unknown".
>6. Deployment of mission critical applications.
>
>Just starters. :) <<
>
>Those aren't features or functionality, those are buzzwords. Do you think adding VFP functionality to .NET would bring increased maturity to the product, for example? It would just be additional code with additional bugs. It's not like you could plug VFP straight in.
>
>I wasn't slamming VFP, only stating that I don't see the benefit (or likelihood) of adding VFP functionality to .NET. Anything you can do in VFP code is already in .NET.
>
>Mike

Mike;

I realize you were not slamming VFP. My viewpoint is that VFP is a product that is known to perform in a number of environments and .NET is an unknown. I would not give consideration into combining the two products, as you would have a true bastard for a tool. Let me call such a concept “contamination”! By attempting to integrate the two technologies you will create additional problems with undesirable consequences. It is better to have separate tools that are capable of working in their own environment.

Tom