>We should suggest that all VFP runtime files be made a part of the operating system. After all, many VB files come with the OS. :)

There are two issues to this, two main reasons this isn't done. For one, it would take a great deal of resources and testing in order to include VFP in the OS which would greatly take away features of future versions of VFP or slip the schedule back so we could not release when we wanted to. The other is that once a newer version of VFP (even a service pack) for VFP is released, the runtime files on the OS would be outdated and you would be back to having to include the latest VFP runtime files used by your app overwriting the OS VFP runtime files. There is really no benefit to doing this, or at least certainly not worth cost in doing it.