PowerBuilder

Unlocks the Chilkat Ftp2 Class

Demonstrates how to unlock the Chilkat Ftp2 functionality. The UnlockComponent method should be called once at the beginning of the program. Once unlocked, all subsequent objects are created in the unlocked state. There is no need to call UnlockComponent for every instance of a Chilkat object.

The object that called UnlockComponent may be discarded (deleted, deallocated, etc.). It does not need to remain in existence for subsequent objects to be already unlocked when created.

Also, the LastErrorText method can be examined to verify that a purchased unlock code was indeed recognized.

PowerBuilder

integer li_rc
integer li_Success
oleobject loo_Glob
integer li_Status

li_Success = 0

// The Chilkat API can be unlocked for a fully-functional 30-day trial by passing any
// string to the UnlockBundle method.  A program can unlock once at the start. Once unlocked,
// all subsequently instantiated objects are created in the unlocked state. 
// 
// <b>After licensing Chilkat, replace the "Anything for 30-day trial" with the purchased unlock code.</b>
// To verify the purchased unlock code was recognized, examine the contents of the LastErrorText
// property after unlocking.  For example:
loo_Glob = create oleobject
li_rc = loo_Glob.ConnectToNewObject("Chilkat.Global")
if li_rc < 0 then
    destroy loo_Glob
    MessageBox("Error","Connecting to COM object failed")
    return
end if
li_Success = loo_Glob.UnlockBundle("Anything for 30-day trial")
if li_Success <> 1 then
    Write-Debug loo_Glob.LastErrorText
    destroy loo_Glob
    return
end if

li_Status = loo_Glob.UnlockStatus
if li_Status = 2 then
    Write-Debug "Unlocked using purchased unlock code."
else
    Write-Debug "Unlocked in trial mode."
end if

// The LastErrorText can be examined in the success case to see if it was unlocked in
// trial more, or with a purchased unlock code.
Write-Debug loo_Glob.LastErrorText


destroy loo_Glob