>This is slightly different way of looking at your question. Here is what I would like to the product to be in 2001:
>
>
>Taken out of Visual Studio.....

Hi John,

I tend to agree with you. Oopishly speaking, vfp doesn't belong in the same class as VC++, VB, and C#. Those are "pure" languages.

VFP's functionality has more simmilarities with access than with any other MS tool:

VFP has a database engine. So does Access.
VFP has a reporting engine. So does Access.
VFP allows you to create full blown apps with no need for third party products. So does Access.

For those who think that I'm saying that VFP is comparable to access in terms of performance, please re-read my message. That's NOT what I'm saying.

VFP cannot become part of the CLR simply because it is MORE than just a programming language.

Have fun!

Alex