>>Larry,
>>
>>A similar issue with this control was covered sometime back in the MSDN News. There are two licenses, however: one for design time, one for run-time. If you're going to add the control either through a prg or AddObject, you need the design time license. Therefore, for distribution, you need to physically add the control rather than say, trying to sub-class (which to me would be preferable in order to avoid versioning issues) it. There are a couple of MS KB articles on this. Most appropriate to me to this issue would be Q139154 and Q192693.
>>
>
>George,
>Thanks for the Q numbers. While I knew about the design time licensing, I didn't realize another license was actually embedded in the form/application when it was saved/compiled. Because it never asked for anything, I assumed (yeah I know :-( ) it didn't need any further information.

Larry,

As I recall, and it's been over a year ago, the MSDN article that I mentioned demonstrated how to, using C++, extract the appropriate license. It's made me wonder, however, whether or not the AddObject() bug is fixed in VFP 7.0. It would be preferable, from design standpoint, to allow us to sub-class these controls rather than to have to add them a separate objects. Lessee...who around here might tell us...:-)