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

Resolved PB 2019 R3 Accessibility Library Error

  1. Issue
0
Votes
Undo
  1. Paul Aspland
    Paul Aspland
  2. PowerBuilder
  3. Sunday, 25 April 2021 15:59 PM UTC

Hi,

I've deployed a 2019 R3 version of my application and, having placed all the runtime components into the same folder as the actual application, I still get an error 'Please check whether Powerbuilder Accessibility library can be located in the path'.

I believe this library is 'PBACC.DLL' and it is a) in the folder I am running the executable from and b) I have added the folder I am running the executable from into the desktop Path variable.

Any ideas people ??.

Thanks,
Paul

 

  1. 64-bit
How to get my seconds screen resolution in Powerbu...
facing fields assignments being disturbed issues w...
Responses (1)
Bruce Armstrong
Bruce Armstrong Accepted Answer Pending Moderation
  1. Sunday, 25 April 2021 18:08 PM UTC
  2. PowerBuilder
  3. # 1

There is a second file (PBAccessibility.dll) according to the runtimes file list in the docs:

https://docs.appeon.com/pb2019r3/application_techniques/ch09s02.html#d0e24197

Also, you can turn off accessibility if it's not something you're actively supporting:

https://docs.appeon.com/pb2019r3/application_techniques/ch08s02.html#Creating

There are some third party drivers that trigger the accessibility, even when you don't need it.  We ran into an issue where one such driver was killing performance of our app because it was causing the accessibility layer to fire an event for every single row and column in a datawindow that contained tens of thousands of rows.

Last thing I'd mentioned is ensuring that the bitness of the files in question match the executable.  We ran into a similar problem (the message appearing where we thought we provided the file) because we had provided the version of the file that supported a different bitness than the app.

Comment
Olan Knight
  1. Olan Knight
  2. Monday, 26 April 2021 20:17 PM UTC
Bruce is, as usual, correct.

We had the same issue until I added both accessibility DLLs into the deployed folder.
  1. Helpful
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.