Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (4)

Resolved URGENT: Richt Text Edit Control

  1. Issue
0
Votes
Undo
  1. MARKOVIC Marko
    MARKOVIC Marko
  2. PowerBuilder
  3. Wednesday, 18 May 2022 09:46 AM UTC

Hi,

PB 21.0.0.1506

 

We use the third part Tx Control 12. in my developpement environnemt in Runtime Mode it works well. On Client Machine i get this error. I controlle that i copy all the dlls and files, the ocx is registered. We don't have took time to migrate to newer version of tx control. It must work now with this version of tx control. Don't understand why on developpemen machine works and not on client machine?

Advice?

PB Runtime Crash
Problems with screen “flickering”
Responses (4)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 18 May 2022 11:55 AM UTC
  2. PowerBuilder
  3. # 1

Hi Markovic;

  PB never supplied a v12 of the TX control. So I assume that your App is using a "paid" version of the control. If that is the case, it might be worthwhile then touching base with the TX vendor about this.

Regards ... Chris

Comment
There are no comments made yet.
Andreas Mykonios
Andreas Mykonios Accepted Answer Pending Moderation
  1. Wednesday, 18 May 2022 11:43 AM UTC
  2. PowerBuilder
  3. # 2

You should check documentation for TX Control 12 to see if this dll is required. I don't have TX Control 12 to help you on this. But be sure not to mix dlls from different versions...

Andreas.

Comment
There are no comments made yet.
MARKOVIC Marko
MARKOVIC Marko Accepted Answer Pending Moderation
  1. Wednesday, 18 May 2022 11:40 AM UTC
  2. PowerBuilder
  3. # 3

I copied podofo.dll to the client machine and it works now but i don't understand why? Nowhere in the documention is written that this dll is needed with 3th part like Tx Control 12, only from Tx Control 15, is that right that this podofo.dll is needed?

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Wednesday, 18 May 2022 17:44 PM UTC
No, the TX v12 and TV v15 in PB require different runtime DLL's. V12 of the TX control runtime DLLs must come from the TX vendor. Do NOT use PB's.
  1. Helpful
There are no comments made yet.
Andreas Mykonios
Andreas Mykonios Accepted Answer Pending Moderation
  1. Wednesday, 18 May 2022 11:13 AM UTC
  2. PowerBuilder
  3. # 4

Hi.

It seems that you are deploying dll's that are part of Powerbuilder's TX Control. From the following link:

Deploying Applications and Components - - Application Techniques (appeon.com)

 
pbrtc.dll, PBTXTEXT.dll, podofo.dll, tp4ole15.ocx, tp15.dll, tp15_bmp.flt, tp15_css.dll, tp15_doc.dll, tp15_dox.dll, tp15_gif.flt, tp15_htm.dll, tp15_ic.dll, tp15_ic.ini, tp15_jpg.flt, tp15_obj.dll, tp15_pdf.dll, tp15_png.flt, tp15_rtf.dll, tp15_tif.flt, tp15_tls.dll, tp15_wmf.flt, tp15_wnd.dll TX Text Control ActiveX 15.0 (32-bit)
pbrtc.dll, PBTXTEXT.dll, podofo.dll, tx4ole28.ocx, tx28.dll, tx28_tls.dll, tx28_wnd.dll, tx28_obj.dll, tx28_ic.dll, tx28_rtf.dll, tx28_htm.dll, tx28_doc.dll, tx28_xml.dll, tx28_css.dll, tx28_pdf.dll, tx28_dox.dll, tx28_xlx.dll, MFC90U.DLL, MSVCR90.DLL, MSVCR120.DLL, MSXML3.DLL, MSXML3A.DLL, MSXML3R.DLL, Microsoft.VC90.CRT.manifest, Microsoft.VC90.MFC.manifest TX Text Control ActiveX 28.0 (32-bit)
pbrtc.dll, PBTXTEXT.dll, podofo.dll, tx4ole28.ocx, tx28.dll, tx28_css.dll, tx28_doc.dll, tx28_dox.dll, tx28_htm.dll, tx28_ic.dll, tx28_obj.dll, tx28_pdf.dll, tx28_rtf.dll, tx28_tls.dll, tx28_wnd.dll, tx28_xlx.dll, tx28_xml.dll, mfc90u.dll, msvcr90.dll, msvcr120.dll, MSXML3.DLL, MSXML3A.DLL, MSXML3R.DLL, Microsoft.VC90.CRT.manifest, Microsoft.VC90.MFC.manifest TX Text Control ActiveX 28.0 (64-bit)

As you don't use Powerbuilder's TX Control be sure that your control doesn't runtime files with the same name. This may result to a runtime mix...

Andreas.

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.