1. Philip Troise
  2. PowerBuilder
  3. Sunday, 23 January 2022 17:34 PM UTC

First)

An update toaddresses the problem that requires  Dw_1.Reset() AND Dw_1.DataObject = “” to be added to the closing of each window containing a datawindow,.  

Dw_1.Reset()

Dw_1.DataObject = “”

 

Second)

PB.ini needing Accessibility=0

 

 

Olan Knight Accepted Answer Pending Moderation
  1. Monday, 31 January 2022 22:03 PM UTC
  2. PowerBuilder
  3. # 1

Are you saying that we need to add the following for EVERY datawidnow on the window when the window closes????????
      Dw_1.Reset()
      Dw_1.DataObject = “”

Why?

Comment
  1. Chris Pollach @Appeon
  2. Monday, 31 January 2022 22:23 PM UTC
Hi Olan ... easy - just add this to their "base" level ancestor (unless of course, your App does not use inheritance... Ahhhhh)!
  1. Helpful
  1. Miguel Leeuwe
  2. Monday, 31 January 2022 23:54 PM UTC
To be honest, I DO believe this might be beneficial, but we don't do this anywhere and everything is working perfectly. Could it be DB related? We're using Oracle.

regards
  1. Helpful 1
  1. Chris Pollach @Appeon
  2. Wednesday, 2 February 2022 19:04 PM UTC
FWIW: I think that this is a large result set issue - either an excessive # rows and/or lots of large columns per row.
  1. Helpful 2
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Sunday, 30 January 2022 19:01 PM UTC
  2. PowerBuilder
  3. # 2

For better performance you could also include

[Datastore Behavior]
UseHwnd=0

"NativePDF_Valid=1" was only supported from PB2017 xx until PB 2019 R, so you might want to leave that out, depending on which version of PB you are using.

Have a read on UseHwnd=0 on https://www.pb.miguell.work/pb-ini/list-entries 
If  you decide to use it, it negatively affects the print of datastores when you want to user print(true, true) and thus have a Printsetup dialog show automatically (see https://community.appeon.com/index.php/qna/q-a/need-for-documentation-on-all-existing-pb-ini-entries )

BTW: I already reported having to set "accessability=0", to be a problem on the support site: https://www.appeon.com/standardsupport/track/view?id=7798 

regards.

MiguelL

Comment
  1. Miguel Leeuwe
  2. Sunday, 30 January 2022 19:17 PM UTC
If that's true, that's aburd, but you're probably right. They should prioritize on 'severity' not on whether a lot of people have noticed a bug.

That explains a lot though.

regrds
  1. Helpful
  1. Roland Smith
  2. Monday, 31 January 2022 15:28 PM UTC
I wonder if UseHwnd=0 has an effect on NativePDF or is it only a problem for printing/Ghostscript.
  1. Helpful
  1. Miguel Leeuwe
  2. Monday, 31 January 2022 15:36 PM UTC
Yes, we really need some good documentation on all of the settings.
  1. Helpful 2
There are no comments made yet.
Philip Troise Accepted Answer Pending Moderation
  1. Sunday, 30 January 2022 18:43 PM UTC
  2. PowerBuilder
  3. # 3

 

I only have the below two options in my pb.ini file

[Data Window]
NativePDF_Valid=1
Accessibility=0

 

 

 

The pb.ini from development has all the ones below. Are there ones I should have that could improve the performance of my runtime application?

[PB]
CompilerWarnings=1
DashesInIdentifiers=1
DatabaseWarnings=1
Maximized=1
PromptOnExit=0
StripComments=0
WebLink1=Community &Q&&A,https://community.appeon.com/
WebLink2=&Online Product Manuals,https://www.appeon.com/documents
WebLink3=PowerBuilder &Demo Apps,https://demo.appeon.com/?Powerbuilder
WebLink4=&PowerBuilder Education,https://www.appeon.com/appeon-u
WebLink5=&Technical Support,https://www.appeon.com/developers/get-help.html
WebLink6=&Latest Product News,https://www.appeon.com/news

EditorFontHeight=10
EditorFontName=Tahoma
PrinterFontHeight=10
PrinterFontName=Courier New
XPStyleTB=1
LatestProductNews=0

[Application]
DefLib=C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexamfe.pbl
WorkingDir=C:\Program Files (x86)\Appeon\PowerBuilder 21.0
$C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexamfe.pbl(examples)=C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexamfe.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexamw3.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexamd2.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexamfn.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexammn.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexamuo.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexamw1.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexamw2.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexamd1.pbl;C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexamsa.pbl;
$C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexbm.pbl(benchmark)=C:\Users\Public\Documents\Appeon\PowerBuilder 21.0\Code Examples\Example App\pbexbm.pbl;

[Window]
GridOn=0
GridShow=1
GridX=8
GridY=8
Status=0

[Menu]

[Database]
AutoQuote=1
Columns=8
NoCatalog=No
ReadOnly=0
ShowIndexKeys=1
ShowReflnt=1
StayConnected=1
TableDir=1
TableListCache=1800
TableSpace=*
TerminatorCharacter=;
HideComments=0
ShowRefInt=1
ODataInPBClassic=1

[Data Window]
GridOn=0
GridShow=0
GridX=8
GridY=8
new_default_datasource=5
new_default_presentation=2
Outline_Objects=1
PreviewOnNew=no
PreviewRetrieve=1
Preview_RetainData=1
PrintOnNew=Yes
PrintPreviewRulers=No
PrintPreviewZoom=100
Ruler=No
Status=0
stored_procedure_build=1
OverlayLineWidth=1

[Library]
ApplicationExplosion=1
ApplicationScripts=1
DeletePrompt=1
DisplayComments=1
DisplayDates=1
DisplaySizes=1
IncludeApplications=1
IncludeDataWindows=1
IncludeFunctions=1
IncludeMenus=1
IncludePipeLines=1
IncludeQueries=1
IncludeStructures=1
IncludeUserObjects=1
IncludeWindows=1
MenuAttributes=1
MenuScripts=1
SaveBackupsOnOptimize=1
WindowAttributes=1
WindowObjects=1
WindowObjectsAttributes=1
WindowObjectsScripts=1
WindowPicture=1
WindowScripts=1
NormalFont=Courier New
NormalFontHeight=10

[Debug]
VariablesWindow=0
WatchWindow=0

[Machine Code]

[SQL Painter]
Hidecomments=0
Tabitem=1

[PB Welcome]
IsEnable = 1
WebLink = news.appeon.com/start.html

Comment
There are no comments made yet.
mike S Accepted Answer Pending Moderation
  1. Sunday, 30 January 2022 17:19 PM UTC
  2. PowerBuilder
  3. # 4
also, even if this does 'fix' your slowness, you should report this as a bug. Some of the capabilities of having ACCESSIBILITY turned on would be really nice to take advantage of if it gets fixed. I'm also not sure if BOTH the new and old versions cause the slowness or only the one. I took the "nuclear option" and turned it completely off in my application. this is what PB help says Accessibility option in the PB.INI file: Accessibility=0: Disable both MSAA and Microsoft UI Automation Accessibility=1: Enable both Accessibility=2: Enable Microsoft UI Automation only Accessibility=3: Enable MSAA only It is recommended that you enable (value is 1) or disable (value is 0) both technologies; if you set the value to 2 or 3 (enable only one of them), some testing tools may not work well with only UIA or MSAA, and may cause the application to malfunction or crash.
Comment
  1. Philip Troise
  2. Sunday, 30 January 2022 17:25 PM UTC
accessibility=0 solved it.

I had that option in and I guess it got lost.



I marked this as solved.

can you report that powerbuilder should work with accessibility on to the developers?
  1. Helpful
  1. mike S
  2. Sunday, 30 January 2022 17:54 PM UTC
  1. Helpful
  1. Christopher Craft
  2. Wednesday, 2 February 2022 00:35 AM UTC
I don't know if this is related but I reported an issue with Appeon about this ( https://www.appeon.com/standardsupport/track/view?id=7784 ). We have found that users with a touchscreen computer that remote into a 2016 server will experience this issue. I would be interested to know if this is what you are experiencing.

Chris Craft
  1. Helpful
There are no comments made yet.
mike S Accepted Answer Pending Moderation
  1. Sunday, 23 January 2022 18:00 PM UTC
  2. PowerBuilder
  3. # 5

have you turned off ACCESSIBILITY in your runtime pb.ini?  

 

add a pb.ini file to your runtime install directory of the application.

Include the following:

[Data Window]
ACCESSIBILITY=0

Comment
  1. Chris Pollach @Appeon
  2. Sunday, 23 January 2022 18:05 PM UTC
Note that this setting only affects DWO's and other controls still use this feature - do the Accessibility DLL is still loaded and active when any PB2019/2021 PB App is running.
  1. Helpful
  1. Miguel Leeuwe
  2. Sunday, 23 January 2022 19:44 PM UTC
Thanks Mike. I wasn't aware of any other options than 0 or 1. Added to my https://www.pb.miguell.work/pb-ini/list-entries

regards
  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.