1. Adam Narten
  2. PowerBuilder
  3. Friday, 25 June 2021 21:42 PM UTC


Our application was experiencing the issue described in this Appeon knowledgebase article where a RichTextEdit control's WordWrap property is checked but the text was still not wrapping. I was able to successfully adjust the pb.ini file on my machine and resolve the problem locally while running through PowerBuilder, however our application deploys on a dedicated build machine using Autocompiler's OrcaScript (orcascr170.exe) which does not have an installation of PowerBuilder. 

Issue: The Autocompiler install does not appear to have a pb.ini configuration file to set "[RichText] PageSizeAsControlSize=1" on our build machine. Is there a command perhaps similar to "set exeinfo property productversion "4"" that can be applied to orcascript so that we can enable WordWrap in our deployed application? Or is there another Autocompiler configuration file that can be modified to set properties such as this? 

Using PowerBuilder/Autocompiler OrcaScript 2017 R3 build 1915   

The reason we build using OrcaScript is because the 2017 PowerBuilder Compiler (PBC) does not provide an option to set the exe icon, which we resolved by building with OrcaScript. Although I'm not sure the pbc would look for a pb.ini file either since it is also a part of the AutoCompiler installation. 

My hope is that there is an option available to set this PageSizeAsControlSize property with our given build environment with OrcaScript.

Thank you!

  1. https://www.appeon.com/developers/get-help/knowledgebase/powerbuilder-richtext-control-wordwrap-property-not-working.html
  2. https://community.appeon.com/index.php/qna/q-a/set-application-icon-when-building-exe-with-pbc170
Accepted Answer
Ken Guo @Appeon Accepted Answer Pending Moderation
  1. Monday, 28 June 2021 07:45 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Adam,


For the “[RichText] PageSizeAsControlSize=1” property you mentioned in the pb.ini file, none of ORCA, PBC, and PBAutoBuild calls “[RichText] PageSizeAsControlSize=1” when you Build or Deploy the application. Only after compilation will the EXE application call “[RichText] PageSizeAsControlSize=1” from the dependent pb.ini file when it runs.


Therefore, when you have compiled the EXE application, you need to manually copy the pb.ini file that contains the “[RichText] PageSizeAsControlSize=1” property to the directory where EXE resides so that when you run EXE on the client machine, the RTE control can enable WordWrap.


And if PBC and PBAutoBuild rely on a property in pb.ini, such as “[PB] DashesInIdentifiers=0” at Build or Deploy, you just need to copy the pb.ini file to the directory where pbc190.exe and pbautobuild210.exe reside.


As for the other thing you mentioned about PBC not providing an option to set the exe icon, we have improved this in PB 2019 R3 and PB 2021 and now PB 2019 R3 and PB 2021 are saving Application ICON in the Application Object source code (which was saved in the PBL file in previous PB versions), so users don’t need to specify ICON again when running ORCA, PBC, or PBAutoBuild in PB 2019 R3 and PB 2021.





  1. Aleš Vojáček
  2. Friday, 1 October 2021 22:58 PM UTC
Hi Ken,

when I'm building (pb2021 aplication) with orca script + pbc210 I have icon in resulting exe.

When I try to compile with PBAutoBuild210.exe where I use this section :

"SourceControl": {

"PreCommand": "",

"Merging": [

{"Target": ".\\konzultace.pbt","LocalProjectPath": ".\\","RefreshPbl": true}


"PostCommand": ""


which recreates all pbls from ws_objects

Then the application does not have icon.

In exported sra there is icon in appicon variable.

Do you have any solution for this?

Thank you

  1. Helpful
  1. Ken Guo @Appeon
  2. Monday, 4 October 2021 02:52 AM UTC
Hi Aleš,

Please open a Support Ticket for this problem. I was able to reproduce this issue on my end.


  1. Helpful
There are no comments made yet.
Adam Narten Accepted Answer Pending Moderation
  1. Monday, 28 June 2021 16:57 PM UTC
  2. PowerBuilder
  3. # 1

Thanks Ken,

I didn't realize that the pb.ini file contained both runtime and compile time settings. That makes sense now that putting the pb.ini file in the client's EXE directory would resolve the issue and indeed it has.

Similarly I now see that the other compiler applications could look for the pb.ini file in their executable directories but it isn't necessary for compiling. It was the lack of the configuration file on installation that made me think they wouldn't use the pb.ini even if it did exist rather than default to a certain a configuration. 

With all of that information I was able to successfully get this working on our deployed application. Thank you so much for your assistance. 


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.