Par2: OCX Interface 1998-06-30 -- Gary Manis I struggled with OCX's at first also but have been getting some good
results of late. The following code snippet I have found to be the key to
"activating" an OCX. I also included the embed title for placement. I use
the window template to place the OCX on and code for it in the embeds.
This particular OCX is from Mabry Software and gives me FTP capability(and
works really well). This example does not use the storage file Clarion
talks about although I have gotten that to work as well. If you try to use
the storage file, use a simple PROP:Open.
I have only worked with 32-bit code. Can't tell you about any differences
in 16-bit.
Another thing I have found is that the OCX may not work correctly on the
first execution after a compile. If the OCX doesn't seem to work properly
after a compile, shut it down (maybe even "End Task") and execute it again.
Then if it doesn't work, you have a problem.
! Start of "Before initializing OLE control"
! [Priority 4000]
?ole{PROP:create}='Mabry.FtpCtrl'
IF ?ole{PROP:license}<>'' ! The control supports licence
?ole{PROP:create}='Mabry.FtpCtrl\!'&?ole{PROP:license}
END
Printed November 21, 2024, 6:37 am This article has been viewed/printed 35183 times. |