1. Richard Lynskey
  2. PowerBuilder
  3. Monday, 10 July 2017 18:44 PM UTC

In 12.6 and earlier, we discovered the hard way that we needed to distribute a pb.ini with the undocumented usehwnd flag set to no to force datastores to actually be nonvisual objects (we had to do this due to datastores using visual handles). Does anyone knows if this has been corrected in the 2017 release?

 

[datastore behavior]
usehwnd=no

 

Thanks!

Accepted Answer
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 11 July 2017 13:16 PM UTC
  2. PowerBuilder
  3. # Permalink

Hi Richard;

   Our Appeon Engineering Team has confirmed that this PB 12.6 feature still works the same in PB 2017. Thus, you will still need to continue add the statement to your PB.INI for the time being to affect DataStore handle allocation.

Regards ... Chris

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 10 July 2017 20:15 PM UTC
  2. PowerBuilder
  3. # 1

Hi Richard;

   I'll double-check with Engineering on this for you!

Regards ... Chris

Comment
  1. Steen Jakobsen
  2. Friday, 14 July 2017 04:26 AM UTC
Hi, 



currently I don't distribute Pb.ini with our application.



where can I find documentation for the different settings supported?



 



thanks Steen

  1. Helpful
  1. Steen Jakobsen
  2. Friday, 14 July 2017 04:27 AM UTC
Hi, 



currently I don't distribute Pb.ini with our application.



where can I find documentation for the different settings supported?



 



thanks Steen

  1. Helpful
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 10 July 2017 19:31 PM UTC
  2. PowerBuilder
  3. # 2

I would like to suggest that all of the poorly documented runtime pb.ini settings be replaced with an easy method to control the settings from code. Having to deploy the pb.ini file with an executable is just plain laziness on the part of Sybase/SAP.

Comment
  1. Richard Lynskey
  2. Monday, 10 July 2017 19:41 PM UTC
If this gets truly considered, pbodb###.ini would be another one that should be considered for that type of deployment change.

  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 10 July 2017 20:22 PM UTC
HI Roland;



  I agree .. also for things like Font control, Extended MAPI, Web Service DW's, etc features that all require PB.INI settings to control. Many of which are either poorly or not documented at all. You are right ... these are left-overs from the old days where less than stellar Engineering approaches were used.



Regards ... Chris

  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.