Erik

I'm missing something about this CLR and hoping somebody will enlighten me.

As far as I can tell, CLR is akin to a Windows extension that will be "there" in Windows by default and can be called on and shared by complying apps, just as Windows handles, API calls, standard ActiveX and fonts are now.

So isn't the CLR sort of like a giant generic VFP runtime dll with calls to be used for common functions by lots of apps?

If so, then if MS included the VFP runtime in the system folder "by default" when windows is installed, we *do* have the advantages of and are sort of part of the CLR?

If I am right, surely the technical question is "how much of VFP's 6Mb runtime dll can go (and needs to go) in the CLR". If we are to use Winforms, I assume that much of the UI can go there. Maybe all of it. How big is the CLR anyway?

Why is this a major deal? I'm not trying to be difficult, I just can't see it.

Regards

JR