Login
Templates, Tools and Utilities
for Clarion Developers
Templates, Tools and Utilities
|
||
|
|
|
Add a comment to an Icetips ArticlePlease add your comments to this article.
Please note that you must provide both a name and a valid email address in order
for us to publish your comment. Comments are moderated and are not visible until they have been approved. Spam is never approved!
Back to article list Search Articles Add Comment Printer friendly Direct link Par2: OCX license string 1999-03-12 -- Kurt Paulikowski For the last few weeks I've been working with Catalyst's OCX's and have finally worked
something up for Alpha testing. When I did this, I ran into a problem with the license,
since it's not "officially" on my tester's machine. After researching and testing, this is
what I found:
1) On your production machine (the one that you ran the authorization software from
Catalyst on), get your license string by adding a scrap of code to any project that's happy
(you should only have to do this once - the license is the same for all the OCX controls
from them).
loc:LicenseText = ?OCX{Prop:License}
... or possibly...
message('License Text: ' & ?OCX{Prop:License})
It should look something like this: ABCDEFGHIJ
2) In the window, under the properties for the OLE, enter the following in the storage
file area:
\!ABCDEFGHIJ
... Note: Don't use quotes. It must be preceded by backslash exclamation mark
characters.
3) Repeat 2 above for each OCX you add to the window.
4) If you are creating your OCX's "on the fly" (from a post by Jim Kane):
?ole1{PROP:create}=CLIP(ocxname)&'\!ABCDEFGHIJ<0>'
NOTES: I have tested 2 but not 4.
Hope that helps those of you that are trying to distribute these things!
Today is November 21, 2024, 7:15 am This article has been viewed 35200 times.
|
|