>What if you had a custom property on a form called foo, then a new version of VFP was released with a new foo property. When the VFP runtime files were updated on a machine from an operation system patch/udpate, your application would break. I think developers need to control when the VFP runtime files are updated on a machine, not an operating system update. There are other factors to consider also, besides that fact that the VFP runtime files are not considered system files and therefore would not be included with any core operating system installation.

Well, that has held true for VB but VB runtimes have shipped with the OS for a long time. OTOH, with VB that's actually been a problem because the installed versions often were out of date. It wouldn't really help now to have VFP 6 runtimes installed by the OS <g>...

I think the story there with VB was that some tools were built with VB. Maybe we need to get some tools that ship with the OS built in VFP. Then the runtime will go with it... Sneaky, sneaky...