1. Louis Mancini
  2. PowerBuilder
  3. Friday, 27 September 2019 11:48 AM UTC

I have a richtextedit control that I'm using to create a RTF report on the fly via sql.

Everything working fine running it in the development studio.  See good image.

Then after a build and test deploy it is not rending the same.  I assume I'm missing a DLL somewhere but tried them all and it still looks like this(see bad image).

We are running Powerbuilder Cloud edition 2019 build 2082.  Deploy is on a windows 10 laptop.

 

Any help would be appreciated.

 

Thanks,

Lou

Attachments (2)
Louis Mancini Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 17:52 PM UTC
  2. PowerBuilder
  3. # 1

I rebuilt and deployed everything as a 32 bit app and it worked.

 

It would be nice for the 64 to work also but its a work around for now.

 

Thanks everyone for all your help.

Lou

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 17:04 PM UTC
  2. PowerBuilder
  3. # 2

Hi Louis;

  FYI:  For RTF Controls and RTE DWO's running from the IDE, the TE or TX control setting is being used. When compiling and running a 64bit PB App EXE, the PB run-time uses the MicroSoft Control! The MS control behaviour is different than either the TE or TX control from the 32bit PB App EXE (unfortunately).

HTH

Regards ... Chris

Comment
  1. Roland Smith
  2. Friday, 27 September 2019 17:10 PM UTC
I'm pretty sure the Microsoft RTE Control is what PowerBuilder used in PB10 and earlier before the TX Text Control was integrated.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Friday, 27 September 2019 17:37 PM UTC
It was the "HighEdit" 3rd party control. However, the MS Text control was used in the WebForm & WinForm App targets I believe.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 14:55 PM UTC
  2. PowerBuilder
  3. # 3

I think you can't. (Correct me anyone if I'm wrong.) As far as I know, there's no option to choose the 32 bit version when having a 64 bit executable.

The only thing to get the same functionality is by using a 32 bit executable.

I'm working on my "own" version of a Rich(er)Text control, based on the work of other people, which I will somehow publish this weekend on GitLab.

I've made that one with C# .net and I guess that there should be a way to make a 64 bit version of it, or making it version independent.

Your problem gives me right away an interesting case to test with!

Comment
There are no comments made yet.
Louis Mancini Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 14:47 PM UTC
  2. PowerBuilder
  3. # 4

I don't think its a path issue as I just tested it on a new laptop that never had powerbuilder anywhere on it.  Plus I used the appeon pb 64bit runtime installer.  Got the same issue.

-------------------------------------------------------------

so when you say:

Is your executable 64 bit?  Yes it is.

Then the difference in RichText would make sense. When creating a 64 bit executable, the richtext used is one which forms part of Windows. When running from the IDE, the RT used is the one you specify in the powerbuilder application object.

-----------------------------------------------------

How do I fix this?

 

 

Comment
There are no comments made yet.
Louis Mancini Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 13:36 PM UTC
  2. PowerBuilder
  3. # 5

Still not working. Same result.

-------------------------------------------

I redeployed all DLLs from C:\Program Files (x86)\Appeon\Shared\PowerBuilder\x64

then added all of these:   What am I missing????

pbrtc190.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
pblab190.ini
pbtra190.dll, pbtrs190.dll
pbpdf190.dll
pbCSI190.dll
pbodw190.dll, pbodt190.dll, Sybase.PowerBuilder.DataSource.OData.dll, Sybase.PowerBuilder.ODataClient.dll, Sybase.PowerBuilder.ODataWrapper.dll
pbjson190.dll, pbhttpclient190.dll, pbrestclient190.dll
pbcrypt190.dll
pboauth190.dll
pbcompression190.dll
pbtheme190.dll, pbjson190.dll (and "theme190" folder)
Comment
  1. Miguel Leeuwe
  2. Friday, 27 September 2019 14:38 PM UTC
Could it be possible that when you run your executable, you are finding an older runtime somewhere in the PATH?

I think something like that happened to me once.

Set the Path to your application's folder as the first folder in your PATH and see if that makes a difference

  1. Helpful
  1. Miguel Leeuwe
  2. Friday, 27 September 2019 14:40 PM UTC
....\x64 ???

Is your executable 64 bit?

Then the difference in RichText would make sense. When creating a 64 bit executable, the richtext used is one which forms part of Windows. When running from the IDE, the RT used is the one you specify in the powerbuilder application object.
  1. Helpful
  1. Miguel Leeuwe
  2. Friday, 27 September 2019 14:43 PM UTC
If your executable is not 64 bit then you should not copy the files from ...\x64 (correct me if I'm wrong)
  1. Helpful
There are no comments made yet.
Louis Mancini Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 12:40 PM UTC
  2. PowerBuilder
  3. # 6

I saw that.  I don't know.  I tried to based on the help documentation.

 

Can someone please send me the exact list of what I need to distribute for richtext.  I think I need to start from scratch.

 

Thanks,

Lou

Comment
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Friday, 27 September 2019 12:30 PM UTC
  2. PowerBuilder
  3. # 7

Comparing the toolbars of the first and second image it looks like the used/found Richtext control is different!

For example the color icon does not show when you run from the IDE.

Do you distribute the required runtime dll's and folders for richtext?

 

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.