Hi Jim,

If you decide to purchase the old richtext, you may find the below useful;

·         For purchasing the old richtext control, please refer to “The old rich text editor (TX Text  Control editor)”  in the local PB 2017 help (Application Techniques -> Data Access Techniques -> Implementing Rich Text -> Using rich text in an application -> Selecting a rich text editor).

·         For how to use the old richtext control in PB 2017, please refer to “To select a rich text editor”  in the local PB 2017 help (Application Techniques -> Data Access Techniques -> Implementing Rich Text -> Using rich text in an application -> Selecting a rich text editor).
 
And kindly please note that only the TX Text Control X14 (Professional or Enterprise edition) is supported in the current PB 2017 (X15 or X14 SP1, SP2 is not supported). 

Usually in order to use the TX Text Control in runtime,  you will need to do the following:

1.    Enter the serial number in Application in PB (Additional Properties-->Richtext Edit tab--->switch to TX control and enter your serial number).    

2.    After compiling the app to .exe, on the client machine, copy the DLLs that are released from the PB runtime package (MSI) installation, and the .exe, etc. to the same folder.

3.    Copy the OCX and DLLs in the TX Text Control bin folder (e.g. C:\Program Files (x86)\Text Control GmbH\TX Text Control 24.0 ActiveX\Bin) from the development machine to the same folder on the client machine as above mentioned.

4.    Open the cmd.exe with “Run as administrator” and manually register tx4ole24.ocx (regsvr32 tx4ole24.ocx).

5.    Or you may skip Step #3 and Step #4, instead directly install the TX Text Control on the client machine.

Kindly please note that since the TX Text Control is no longer included in PB 2017, so it is unavoidable to manually register the OCX or install the TX  Text Control on the client machine. We appreciate your understanding. 

Regards,

Mark Lee

Hi Jim,

I don't have the answer, but I suspect you will need to install the TX Text OCX control on each user's machine for them to be able to use it.  With the 12.6 Runtime Packager you could choose Rich Text support and it would include all the required files in the deployment installer.  I suspect it also registered the OCX control as part of its installation.

Since Appeon don't have a license to distribute the TX Text control I doubt that the new Runtime Packager will do any of that for you so you will have to treat it like any other redistributable OCX control and either have a separate installer for the TX Text OCX control or roll it into your own Installer if you don't use the Runtime Packager.

I hope that helps.

Daryl.

Hi James,

You can find more information related to this control in the PowerBuilder help files. You can find it in: Objects and Controls > System Object Properties, Events, and Functions > RichTextEdit Control.

Some more information is also available a the "Application Techniques.pdf" document available at: https://www.appeon.com/system/files/product-manual/application_techniques.pdf. On Page 261, Implementing Rich Text.

Regards,

You need to make sure you have version X14 rather than newer version X15 and make sure it is a paid version and enter your TX TextControl in the PowerBuilder activation screen as outlined in the PowerBuilder documentation.  

Since you are not using RichText DataWindow you might want to consider simply embedding TX TextControl as an external object into your app.  This way if there are any problems TX TextControl vendor would be in a better position to resolve your issues.