Is the MSCOMCTL OCX installed on the non-dev machine? MSCOMCTL can be distributed to non-dev machines.


>I still get the "Not licenced for use" error under runtime. The problem is as developers, a licence in stalled with VFP for blanket use of the control on your own development machine. So we have to subclass the control onto a form before it works on a non-dev machine. My gripe here is I can only find a way to make this work on an SCX based form and not a PRG based form. Which, BTW, makes ZERO sense to me.
>
>>I made these little changes and a brief (though not scientific) test showed the form.
>>
>>>This is maintenance work on a VFP7 app. I know all about having to subclass an OCX like MSComm32 onto a form to avoid the "Class not licensed" error [the class IS registered, that is NOT the problem]. If I drop this OCX on a form and run the form it works under runtime on a non-developer machine. What aggravates the hell out of me is it won't work if the form is PRG based. For example, is there any way to make this work:

>>
>>public loform
>>SET TALK OFF
>>SET EXCLUSIVE off
>>SET MULTILOCKS on
>>SET DELETED on
>>SET CENTURY on
>>
>>loForm = CREATEOBJECT("LineDisplay")
>>loform.ADDOBJECT('oComm','oleCommControl','MSCOMMLib.MSComm.1')
>>loForm.Show(1)
>>
>>DEFINE CLASS LineDisplay AS Form
>>   DataSession = 2
>>   PROTECTED PROCEDURE Init
>>   ENDPROC
>>   PROCEDURE Release
>>      RELEASE THIS
>>   ENDPROC
>>ENDDEFINE
>>
>>DEFINE CLASS oleCommControl AS olecontrol
>>ENDDEFINE

>>
>>>Trying with the AddObject() and commenting out the ADD OBJECT will not work either. By making this work, I mean on a non-developer machine under runtime. My preference is getting this to work in a PRG class instead of an SCX, but I will quit fighting this if the SCX is the only way to go. TIA!