The show or edit command instantiates the OCX. You may be able to get away with using the newinstance command to instantiate the signature associate with the OCX, as long as the OCX itself has no display requirement. variables handle v_handle endvariables newinstance "OCXSIG", v_handle v_handle->Operation as opposed to using $ocxhandle.

Unfortunately, as soon as the print command goes, uf tries to load ugui.dll - and then throws a -400. Running the same component from Windows is fine - so I'm pretty confident it's the OCX that's the culprit.... Hence I'm looking for alternatives... The way it's looking at the moment; Grab a 3gl (DLL) and send it the string I'd like to encode - a BMP/IMG is created on disk. Load the BMP/IMG into the component and 'print' to pdf file output Unless there's a better solution out there? Knut

Hi,as for me, I am testing the related pdf417 reading these days. But first i need to produce the PDF417 embedded font.Who can tell me how to use OCX to do this.I am totally a green hand on this field. Any suggestion will be appreciated. Thanks in advance.