>You might remember that I asked that same question a long while back. Given
>the fact that VFPCOM is just shipping now, I'm not so sure your answer is
>the right one <s>...
>
I won't go into too many details on this, but there are very valid reason for this. There are also support issues that go towards this. Microsoft, specifically the VFP team, can post an update to VFPCOM.DLL at any time, for example, if a problem was found binding to some COM object and it turned out to be a bug in VFPCOM.DLL, etc. In the end, it really doesn't matter if it's in a DLL or native to the language, it works, and it's available.