>>>>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.
>>>
>>>It was actually the same point. You made it a mere 90 seconds before me. < s >
>>
>>Freak things do happen...Kent State/Indiana...Hampton/Iowa State.< g >
>
>Looks like Illinois made it past thier opponent. Too bad. That could have been fun with the Illini supporters around here. < gd&rvvf >

Hey! I resemble that remark.:-) BTW, as of this minute, your's truly is in the lead in the office pool. Got 13 of 16 yesterday.:-)

>>
>>>FYI, both those controls have license information embedded under HKEY_CLASSES\ROOT\Licenses. Without doing too much digging, I didn't get the actual registry keys for them but you can find them (if you really, really want to) by going through the SRG files in your System/System32 directory.
>>
>>As I understand it, there are only a few ActiveX controls that have two different licenses (one for design and one for run-time). Two of them I've mentioned before. These are the only ones (so far < gt hedges his bets here >) that I'm currently aware of.
>
>I thought all of the MS controls were that way. All of the license information for them is included in the registry and trying to instantiate one at run-time throws an error.

To be frank (who?< g >), Larry, I really don't know for sure. AFAIK, however, I think that some controls (from MS) only have one license, and as long as you distribute control you're fine. The Common Dialogs Control, however, has to have a physical presence on your form.

As I said to Bill, there may be a KB article on sub-classing ActiveX controls, but I can't recall if that's where I picked the technique up or not.

>Other products (e.g. True DBGrid) use LIC files. If they aren't there during development, you can't add it to the form.