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

Resolved PB.INI and ACCESSIBILITY=0

  1. Advice
0
Votes
Undo
  1. Aron Cox
    Aron Cox
  2. PowerBuilder
  3. Tuesday, 26 April 2022 08:29 AM UTC

PowerBuilder 2019 R3 build 2728, and other older versions.

We've started getting more customers with random crashes in the past few months. I suspect many, if not all, are related to the known issue with PowerBuilder and Windows Accessibility, and that somethignh has been turning on some acessibility setting in the background. I have seen there used to an option to set ACCESSIBILITY=0 in the PB.INI to fix this issue. This has led me to a couple of questions, I hope someone can help me with:

* I know there have been a bunch of changes to acessibility in PowerBuiler 2019 R3, does the above INI setting still do something in PowerBuilder 2019 R3?

* We don't currently have a PB.INI, is it just a matter of creating new new empty one with a [Data Window] section and a single ACCESSIBILITY=0 under it and copying it to the same folder as the executable?

Thank you :-)

 

 

  1. PowerBuilder
Probable bug with CloseUserObject and webbrowser
Instance Variable
Accepted Answer
Andreas Mykonios
Andreas Mykonios Accepted Answer Pending Moderation
  1. Tuesday, 26 April 2022 09:06 AM UTC
  2. PowerBuilder
  3. # Permalink

* I know there have been a bunch of changes to acessibility in PowerBuiler 2019 R3, does the above INI setting still do something in PowerBuilder 2019 R3?

Yes.

* We don't currently have a PB.INI, is it just a matter of creating new new empty one with a [Data Window] section and a single ACCESSIBILITY=0 under it and copying it to the same folder as the executable?

Yes.

Comment
Load more comments
Andreas Mykonios
  1. Andreas Mykonios
  2. Tuesday, 26 April 2022 09:22 AM UTC
As many options in pb.ini are not well documented you may take a look to the great job Miguel Leeuwe has done (https://www.pb.miguell.work/pb-ini/list-entries). Another one that may be interesting if you are using datastores is the: [DataStore Behavior] -> UseHwnd... But read carefully the comments of Miguel for the specific before deciding to use it.

Andreas.
  1. Helpful 2
Aron Cox
  1. Aron Cox
  2. Saturday, 30 April 2022 06:33 AM UTC
Thank you, I tried the UseHwnd option but the user reported our application immediately crashed :(
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Saturday, 30 April 2022 11:18 AM UTC
Hi Aron,

That's pretty weird. UseHwnd could affect printing of a Datastore or (possibly) failing retrieve of a Datastore with WEB-API, but "crashing immediately" simply doesn't seem plausible.

Did you try the option on your own PC when running the application?

regards,

MiguelL
  1. Helpful
There are no comments made yet.
Responses (2)
Connie Dove
Connie Dove Accepted Answer Pending Moderation
  1. Friday, 29 April 2022 18:37 PM UTC
  2. PowerBuilder
  3. # 1

Question on the use of the pb.ini.  Currently we have a couple applications running from the same location, all the runtime files, exes and pbds are in the same folder.  We have seperate INI files set up for the applications that are used for database connection info.  Would we need to have a seperate pb.ini for each application, or just 1 for all.  Or can we add the entries into the application INI file?

 

We are having issues with applications crashing for no reason for our users, but the developers have been unable to duplicate the issue.

Comment
John Fauss
  1. John Fauss
  2. Friday, 29 April 2022 18:55 PM UTC
The PB runtime uses the first pb.ini file it finds (if any), so if you have a common location/folder that several PB apps use for their exe's and pbd's/dll's, then a pb.ini file added to this folder would be seen and used by all apps. The options referred to in this thread MUST reside in a file named pb.ini, for that is what the runtime searches for and uses.
  1. Helpful 2
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.