>Sorry for re-hashing what has been talked to death but I have not been albe to check UT much of late.
>
>1. Is VFP going to be part of the CLR?

It doesn't appear that VFP7 will use the CLR. VFP8 is still up in the air from what I have heard.

>2. If we are not going to be in the CLR are we bothered about it?

Yes. There are advantages to using the CLR, which I would like VFP8 to have a compile time choice for. These advantages include:
1) VFP will run on any version of Windows or OS that the CLR is ported to. We might get things like a CE or Linux port for free
2) Since the CLR will be included in the OS (from what I have heard) this will make deployments of applications much easier because you will no longer need to install the VFP runtime on thousands of PCs. If your customers download your application from the web they won't need to download a multi MB runtime.

Some opponents to the CLR have raised the argument that a CLR/VFP app will be basically be VB so why do this? Well if you are designing n-tier apps with XML or ADO your apps already look much like VB.

>Some earlier threads I looked at seemed to be saying that the CLR implementation of VB is going to be pretty close to what we are used to in VFP anyway.

Can you point me to the these messages?