1. Troy Cowan
  2. PowerBuilder
  3. Wednesday, 23 August 2023 15:42 PM UTC

Hi. We have two different powerbuilder applications we support. I recently installed one of them to a new Windows 10 PC, and when I go to run it, I get the "Please check whether PowerBuilder Accessibility library can be located in the path." error dialog. 

After looking into it a bit, I know this has to do with supporting Windows Accessibility. I discovered that with the first application, we are installing the pbacc.dll and pbaccessibility.dll with our application, and we don't install either with our second application that is seeing the error. 

I then tried different combinations of supplying the two .dlls, and I have found that I only need to supply the pbacc.dll to make the error go away. I also understand that setting Accessibility=0 in the pb.ini file might also make the error go away, although so far for me this has not worked. 

So I have two sets of questions: 

Regarding the .dlls: what does pbacc.dll do vs pbaccessibility.dll? Is it safest to just add them both to my application?

Regarding pb.ini: Should setting Accessibility=0 in the ini file really make the error go away? What section of the ini file should it go in? And does this setting take effect at build time or at run time? 

Troy Cowan Accepted Answer Pending Moderation
  1. Wednesday, 30 August 2023 14:33 PM UTC
  2. PowerBuilder
  3. # 1

Still hoping for some help here. 

 

Can anyone tell me the cost or benefit of including BOTH pbacc.dll AND pbaccessibility.dll with my app vs. pbacc.dll ONLY? I seem to avoid my error message with just including pbacc.dll, but there could be something else going on that I can't see. 

 

Can anyone tell me why I still see the error dialog when i set ACCESSIBILITY=0 in my pb.ini file? Seems like only the presence/absence of pbacc.dll affects whether I see the error dialog. 

Comment
  1. Miguel Leeuwe
  2. Wednesday, 30 August 2023 15:20 PM UTC
hi Troy,

Well if I understood well, obviously, the benefit of it is not getting the error. I don't know what goes on under the hood. In previous versions, we've had more DLLs that had to be included while it didn't make any sense.

regards
  1. Helpful
  1. Troy Cowan
  2. Wednesday, 30 August 2023 16:05 PM UTC
At the risk of dragging this on for longer than it is worth: no, I don't get a benefit of not getting the error by including pbaccessibility.dll.

If I include neither DLL, I get the error

If I include ONLY pbaccessibility, I get the error

If I include ONLY pbacc, I don't get the error

If I include BOTH, I don't get the error.



So I'm 99% sure I will include pbacc. I'm 50% sure I will include pbaccessibility, because it doesn't seem to do me any good or any harm either. That's why I would like to know what its all about if possible.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Thursday, 24 August 2023 11:59 AM UTC
  2. PowerBuilder
  3. # 2

Hi,

I have a pb.ini file like this, which I distribute to my installed applications (in the folder where the EXE file is).

Are you distributing the PB.INI?

PB.INI distributed with my apps:

[PB]
UseSimpleMAPI=No

[DataStore Behavior]
UseHwnd=No

[Data Window]
ACCESSIBILITY=0
ForgetColumnKeyboardLayout=Yes

[RichText]
PageSizeAsControlSize=1
Comment
  1. Miguel Leeuwe
  2. Thursday, 24 August 2023 16:42 PM UTC
There's been quite a few problems with touch screens. Most of them were resolved by disabling the touch screen feature in windows.
  1. Helpful
  1. Chris Pollach @Appeon
  2. Wednesday, 30 August 2023 18:04 PM UTC
Hi Troy;

Yes, those two files are required - even if you have the accessibility set to off in your custom PB.ini file as they are checked for their presence by the PBVM at App start-up regardless.

FYI: https://docs.appeon.com/pb2022/application_techniques/PowerBuilder_runtime_files.html

Regards ... Chris
  1. Helpful 1
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 23 August 2023 19:17 PM UTC
  2. PowerBuilder
  3. # 3

Hi Troy, If you do not need to use accessibility then you should disable it by setting it to 0 in the INI.  When it is set to zero, no need to distribute the accessibility runtime DLLs.

Comment
  1. Shenn Sellers
  2. Thursday, 24 August 2023 16:23 PM UTC
You need to distribute that pb.ini file in the same directory as you distribute your applications. Can't just have it on your development PC.
  1. Helpful 1
  1. Troy Cowan
  2. Thursday, 24 August 2023 16:54 PM UTC
OK, thank you. Is there anything else I need to do? I have tried adding pb.ini to the same folder as my .exe and it does not fix the issue.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Tuesday, 5 September 2023 16:56 PM UTC
This will be fixed in PB 2022 R3. Currently, there is a bug and those DLLs are required even though you disabled accessibility.
  1. Helpful
There are no comments made yet.
John Fauss Accepted Answer Pending Moderation
  1. Wednesday, 23 August 2023 16:20 PM UTC
  2. PowerBuilder
  3. # 4

Hi, Troy - 

The following link may help resolve some of the questions you have raised regarding the pb.ini file:

    https://docs.appeon.com/pb2022/pbug/PBINI_settings.html

Best regards, John

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.