Alaska Software Inc. - Same Control diferent problem?! HELP!
Username: Password:
AuthorTopic: Same Control diferent problem?! HELP!
Paulo GaitaSame Control diferent problem?! HELP!
on Tue, 04 Mar 2008 18:16:41 +0000
Hi,

Thanks to you guys, specialy Pablo Botella, thanks again Pablo, I managed to 
get everything running, so much so that I recomend it be bought.

Now I have another problem. The components have been bought and are working 
perfectly in the development machine.

The problems start when I try to install the final product, one of our APPs, 
on another computer.
We allways get an error stating that the controls can't be created.
After a few goes we found that it was missing the ActiveX License 
information.
So I tied it the way Codejock's documentation says it should be done. Create 
an ActiveX Object that comes with each of controls and pass it the license 
information has per the LIC file.
And, of course, it doesn't work. I've contated Codejock's support but they 
don't oficially support any such thing has Alaska XBase++ so I'm not holding 
my breath.

I think the problem has, once again, to do with the GUI Thread.
The licensing object isn't a GUI object, but the Controls themselfs are.
For the licensing object I have to use ActiveXObject:create(), for the 
others I use XbpActiveXControl:new() .
If I use the :useGUIThread := .F. workaround the control freezes, so that 
isn't the answer.

Is there anyway to get GUIThread ID and create the licensing object to run 
on it ?
I am not entirely sure this is the issue, but I know the Licensing component 
is running properly, and I also know the Control is properly registred ( i 
placed the LIC files together with it and all problems went away ), so it 
has to be something related to the XBase++ Threading model.

PLEASE HELP!!

Best regards,
Paulo Gaita
Mark Sergent Re: Same Control diferent problem?! HELP!
on Tue, 04 Mar 2008 12:03:47 -0800
Hi Paulo,

have run into this on a few controls where they use a licencing file
primarily for VB etc and dont inform you of how to get the license
information into a language like xbase.

I use the following tool to get this information:

comlicencefinder.exe

found at: http://www.codeproject.com/KB/COM/ObtainActiveXLicenceInfo.aspx

It will give you a list of all of the registered activex controls on your
machine, if you right click on the control name and select get info it will
put the licence text fromt he control required for xbase's licensing
syntax.

I usually copy it and past it into my editor and then code it as follows.

oControl := xbpActiveXControl():new(params)
oControl :CLSID := "{Control ID}"
oControl :license := "license text from comlicencefinder"
oControl :create()

Hope this helps

Mark Sergent
InnSource Solutions Inc.
mark@innsourcesolutions.com

------------------------------
On Tue, 04 Mar 2008 18:16:41 +0000, Paulo Gaita wrote:

> Hi,
> 
> Thanks to you guys, specialy Pablo Botella, thanks again Pablo, I managed to 
> get everything running, so much so that I recomend it be bought.
> 
> Now I have another problem. The components have been bought and are working 
> perfectly in the development machine.
> 
> The problems start when I try to install the final product, one of our APPs, 
> on another computer.
> We allways get an error stating that the controls can't be created.
> After a few goes we found that it was missing the ActiveX License 
> information.
> So I tied it the way Codejock's documentation says it should be done. Create 
> an ActiveX Object that comes with each of controls and pass it the license 
> information has per the LIC file.
> And, of course, it doesn't work. I've contated Codejock's support but they 
> don't oficially support any such thing has Alaska XBase++ so I'm not holding 
> my breath.
> 
> I think the problem has, once again, to do with the GUI Thread.
> The licensing object isn't a GUI object, but the Controls themselfs are.
> For the licensing object I have to use ActiveXObject:create(), for the 
> others I use XbpActiveXControl:new() .
> If I use the :useGUIThread := .F. workaround the control freezes, so that 
> isn't the answer.
> 
> Is there anyway to get GUIThread ID and create the licensing object to run 
> on it ?
> I am not entirely sure this is the issue, but I know the Licensing component 
> is running properly, and I also know the Control is properly registred ( i 
> placed the LIC files together with it and all problems went away ), so it 
> has to be something related to the XBase++ Threading model.
> 
> PLEASE HELP!!
> 
> Best regards,
> Paulo Gaita
Paulo GaitaRe: Same Control diferent problem?! HELP!
on Wed, 05 Mar 2008 17:16:59 +0000
And again one of you comes through!!

Thanks Mark, it worked like a charm!

Best regards,
Paulo Gaita
"Mark Sergent" <mark@innsourcesolutions.com> wrote in message 
news:17wojcon0404f.1jqjr6mqz149r$.dlg@40tude.net...
> Hi Paulo,
>
> have run into this on a few controls where they use a licencing file
> primarily for VB etc and dont inform you of how to get the license
> information into a language like xbase.
>
> I use the following tool to get this information:
>
> comlicencefinder.exe
>
> found at: http://www.codeproject.com/KB/COM/ObtainActiveXLicenceInfo.aspx
>
> It will give you a list of all of the registered activex controls on your
> machine, if you right click on the control name and select get info it 
> will
> put the licence text fromt he control required for xbase's licensing
> syntax.
>
> I usually copy it and past it into my editor and then code it as follows.
>
> oControl := xbpActiveXControl():new(params)
> oControl :CLSID := "{Control ID}"
> oControl :license := "license text from comlicencefinder"
> oControl :create()
>
> Hope this helps
>
> Mark Sergent
> InnSource Solutions Inc.
> mark@innsourcesolutions.com
>
> ------------------------------
> On Tue, 04 Mar 2008 18:16:41 +0000, Paulo Gaita wrote:
>
>> Hi,
>>
>> Thanks to you guys, specialy Pablo Botella, thanks again Pablo, I managed 
>> to
>> get everything running, so much so that I recomend it be bought.
>>
>> Now I have another problem. The components have been bought and are 
>> working
>> perfectly in the development machine.
>>
>> The problems start when I try to install the final product, one of our 
>> APPs,
>> on another computer.
>> We allways get an error stating that the controls can't be created.
>> After a few goes we found that it was missing the ActiveX License
>> information.
>> So I tied it the way Codejock's documentation says it should be done. 
>> Create
>> an ActiveX Object that comes with each of controls and pass it the 
>> license
>> information has per the LIC file.
>> And, of course, it doesn't work. I've contated Codejock's support but 
>> they
>> don't oficially support any such thing has Alaska XBase++ so I'm not 
>> holding
>> my breath.
>>
>> I think the problem has, once again, to do with the GUI Thread.
>> The licensing object isn't a GUI object, but the Controls themselfs are.
>> For the licensing object I have to use ActiveXObject:create(), for the
>> others I use XbpActiveXControl:new() .
>> If I use the :useGUIThread := .F. workaround the control freezes, so that
>> isn't the answer.
>>
>> Is there anyway to get GUIThread ID and create the licensing object to 
>> run
>> on it ?
>> I am not entirely sure this is the issue, but I know the Licensing 
>> component
>> is running properly, and I also know the Control is properly registred 
>> ( i
>> placed the LIC files together with it and all problems went away ), so it
>> has to be something related to the XBase++ Threading model.
>>
>> PLEASE HELP!!
>>
>> Best regards,
>> Paulo Gaita
Anand GuptaRe: Same Control diferent problem?! HELP!
on Mon, 07 Apr 2008 13:31:54 +0530
Thanks Mark for the EXE link.

I also recall a programme suggested by someone few years ago which would 
list all the COM/ActiveX installed on a particular computer and I could find 
methods/properties etc details from the same. It also use to generate a 
HLP/CHM file for the selected COM/ActiveX

Forgetting the name.

Anand

"Mark Sergent" <mark@innsourcesolutions.com> wrote in message 
news:17wojcon0404f.1jqjr6mqz149r$.dlg@40tude.net...
> Hi Paulo,
>
> have run into this on a few controls where they use a licencing file
> primarily for VB etc and dont inform you of how to get the license
> information into a language like xbase.
>
> I use the following tool to get this information:
>
> comlicencefinder.exe
>
> found at: http://www.codeproject.com/KB/COM/ObtainActiveXLicenceInfo.aspx
>
> It will give you a list of all of the registered activex controls on your
> machine, if you right click on the control name and select get info it 
> will
> put the licence text fromt he control required for xbase's licensing
> syntax.
>
> I usually copy it and past it into my editor and then code it as follows.
>
> oControl := xbpActiveXControl():new(params)
> oControl :CLSID := "{Control ID}"
> oControl :license := "license text from comlicencefinder"
> oControl :create()
>
> Hope this helps
>
> Mark Sergent
> InnSource Solutions Inc.
> mark@innsourcesolutions.com
>
> ------------------------------
> On Tue, 04 Mar 2008 18:16:41 +0000, Paulo Gaita wrote:
>
>> Hi,
>>
>> Thanks to you guys, specialy Pablo Botella, thanks again Pablo, I managed 
>> to
>> get everything running, so much so that I recomend it be bought.
>>
>> Now I have another problem. The components have been bought and are 
>> working
>> perfectly in the development machine.
>>
>> The problems start when I try to install the final product, one of our 
>> APPs,
>> on another computer.
>> We allways get an error stating that the controls can't be created.
>> After a few goes we found that it was missing the ActiveX License
>> information.
>> So I tied it the way Codejock's documentation says it should be done. 
>> Create
>> an ActiveX Object that comes with each of controls and pass it the 
>> license
>> information has per the LIC file.
>> And, of course, it doesn't work. I've contated Codejock's support but 
>> they
>> don't oficially support any such thing has Alaska XBase++ so I'm not 
>> holding
>> my breath.
>>
>> I think the problem has, once again, to do with the GUI Thread.
>> The licensing object isn't a GUI object, but the Controls themselfs are.
>> For the licensing object I have to use ActiveXObject:create(), for the
>> others I use XbpActiveXControl:new() .
>> If I use the :useGUIThread := .F. workaround the control freezes, so that
>> isn't the answer.
>>
>> Is there anyway to get GUIThread ID and create the licensing object to 
>> run
>> on it ?
>> I am not entirely sure this is the issue, but I know the Licensing 
>> component
>> is running properly, and I also know the Control is properly registred 
>> ( i
>> placed the LIC files together with it and all problems went away ), so it
>> has to be something related to the XBase++ Threading model.
>>
>> PLEASE HELP!!
>>
>> Best regards,
>> Paulo Gaita
Mark Sergent Re: Same Control diferent problem?! HELP!
on Tue, 08 Apr 2008 01:37:37 -0700
There are a couple of tools I user to document controls.

DocToolLib from - http://www.angelfire.com/80s/philipsoft/

and 

HelpKit Com Assistant from - http://www.devcomponents.com/comassistant/


Mark Sergent
InnSource Solutions Inc.
www.innsourcesolutions.com
mark@innsourcesolutions.com


On Mon, 07 Apr 2008 13:31:54 +0530, Anand Gupta wrote:

> Thanks Mark for the EXE link.
> 
> I also recall a programme suggested by someone few years ago which would 
> list all the COM/ActiveX installed on a particular computer and I could find 
> methods/properties etc details from the same. It also use to generate a 
> HLP/CHM file for the selected COM/ActiveX
> 
> Forgetting the name.
> 
> Anand
> 
> "Mark Sergent" <mark@innsourcesolutions.com> wrote in message 
> news:17wojcon0404f.1jqjr6mqz149r$.dlg@40tude.net...
>> Hi Paulo,
>>
>> have run into this on a few controls where they use a licencing file
>> primarily for VB etc and dont inform you of how to get the license
>> information into a language like xbase.
>>
>> I use the following tool to get this information:
>>
>> comlicencefinder.exe
>>
>> found at: http://www.codeproject.com/KB/COM/ObtainActiveXLicenceInfo.aspx
>>
>> It will give you a list of all of the registered activex controls on your
>> machine, if you right click on the control name and select get info it 
>> will
>> put the licence text fromt he control required for xbase's licensing
>> syntax.
>>
>> I usually copy it and past it into my editor and then code it as follows.
>>
>> oControl := xbpActiveXControl():new(params)
>> oControl :CLSID := "{Control ID}"
>> oControl :license := "license text from comlicencefinder"
>> oControl :create()
>>
>> Hope this helps
>>
>> Mark Sergent
>> InnSource Solutions Inc.
>> mark@innsourcesolutions.com
>>
>> ------------------------------
>> On Tue, 04 Mar 2008 18:16:41 +0000, Paulo Gaita wrote:
>>
>>> Hi,
>>>
>>> Thanks to you guys, specialy Pablo Botella, thanks again Pablo, I managed 
>>> to
>>> get everything running, so much so that I recomend it be bought.
>>>
>>> Now I have another problem. The components have been bought and are 
>>> working
>>> perfectly in the development machine.
>>>
>>> The problems start when I try to install the final product, one of our 
>>> APPs,
>>> on another computer.
>>> We allways get an error stating that the controls can't be created.
>>> After a few goes we found that it was missing the ActiveX License
>>> information.
>>> So I tied it the way Codejock's documentation says it should be done. 
>>> Create
>>> an ActiveX Object that comes with each of controls and pass it the 
>>> license
>>> information has per the LIC file.
>>> And, of course, it doesn't work. I've contated Codejock's support but 
>>> they
>>> don't oficially support any such thing has Alaska XBase++ so I'm not 
>>> holding
>>> my breath.
>>>
>>> I think the problem has, once again, to do with the GUI Thread.
>>> The licensing object isn't a GUI object, but the Controls themselfs are.
>>> For the licensing object I have to use ActiveXObject:create(), for the
>>> others I use XbpActiveXControl:new() .
>>> If I use the :useGUIThread := .F. workaround the control freezes, so that
>>> isn't the answer.
>>>
>>> Is there anyway to get GUIThread ID and create the licensing object to 
>>> run
>>> on it ?
>>> I am not entirely sure this is the issue, but I know the Licensing 
>>> component
>>> is running properly, and I also know the Control is properly registred 
>>> ( i
>>> placed the LIC files together with it and all problems went away ), so it
>>> has to be something related to the XBase++ Threading model.
>>>
>>> PLEASE HELP!!
>>>
>>> Best regards,
>>> Paulo Gaita