>Do you understand the implications for VFP if it does participate in the CLR?
>
>- No native data access. This means everything goes through ADO+
>- No macro expansion. I know that it's not generally a good idea to use macro expansion, but sometimes it is the best solution.
>- How do we then differentiate ourselves from VB?

That is easy - VFP is a longer acronym! :) (I am trying to duck after that one)

>
>
>>
>>My feeling is that the Common Language Runtime (CLR) is a strategic move. In distributing applications, I'd like the ability to run them already present on a client's server. It's a perception thing with clients. Our reality may be that it makes no difference. Their reality may be that VFP is out of step.
>>
>>I'm hoping to hear that Version 8 will be moving toward a CLR compiler. In 2 years we should know if it will take hold. I think it will with the resources MS is devoting to it.
>>