>>I think that with the controls from MS, the answer may be yes. There's usually a CurVer registry key and the CLSIDs of the two match. However, even with MS controls, if you update the control locally, then you need to distribute and install the new control on the target to avoid versioning problems.
>>
>>The most common workaround, doesn't always "work" because of licensing issues. The idea is to sub-class the control in a prg file, then add it at run-time. However, with the Common Dialogs Control and the MSComm32 control, licensing problems (design vs. runtime) you can't do this.
>
>That's interesting and something to think about and watch for, especially in light of Larry's comments. The whole "COM" philosophy certainly has its plusses and minuses. :-)

Well, Larry's point was essentially the same one I was making. When I was writing Obj2Bmp I wanted it to work with both VFP 5.0 and 6.0. However, since it utilized the TreeView and the ImageList, and the versions of the controls (including ProgIDs) were different. The solution was to simply subclass the controls, determining which one to instantiate at run-time. I don't know if there are licensing issues with those controls or not, but in this instance, it really didn't matter since the application was designed to be used in design mode.