i would like to know more about this aswell

taking advantage of this question, as stated in another thread, i'm having trouble enabling this command in the pb.ini on my application:

[DataStore Behavior]
UseHwnd=no

if i enable this on my pb.ini and starting my app from a compiled .EXE i'm getting trouble accessing a remote datastore accessed via restclient. If i run it from the IDE with the same command enabled it's working fine.
In particular this is the code i'm using which fails:

RESTClient inv_RestClient
inv_RestClient = CREATE RESTClient
inv_RESTClient.SetRequestHeader ("Content-Type", "application/json;charset=UTF-8")
inv_RestClient.Setrequestheader( "Accept-Encoding", "gzip")

datastore dss
dss = create datastore
dss.dataobject='dss_startreg_new_find'
ls_Request_Url = ls_url+"startregnewfind/Retrieve?codaz=" + ls_codaz
inv_RestClient.retrieve(dss, ls_Request_Url)
if dss.rowcount( ) > 0 then
    messagebox("SUCCESS!", "")
else
    messagebox("FAILED!", "")
end if
destroy dss
destroy inv_RestClient

if i put the pb.ini in the client folder where is the app .exe the retrieve always failing. If i remove it, it's working fine.
This is a pity cos i've notice a general improvement of my application with that command enabled.

Hi Everyone;

  Just an FYI ...

1) The STD Framework uses direct calls to PBVM and PBSHR DLLs.  Have a look in the framework for these references and how they are being used. The framework has tons of in-line documentation on how & why these calls are being used.

2) The Framework has a sub-folder called INI. In there, you will find a PB.INI with most of the options that I know about and appropriate comments around each.

3) The STD Framework's OrderEntry Demo App uses quite a few of the above. So a good place to to review actual working code.

4) The "nc_app_Controller_master" NVUO in the "STD_FC_PB_Base" PBL has almost all the MS-Window's API functions defined in it that most any PB App would possibly use.

Framework: http://sourceforge.net/projects/stdfndclass/files/FrameWork/Integrated

Demo App: http://sourceforge.net/projects/stdfndclass/files/Applications/PowerBuilder/OrderEntry

PS: I will be uploading a newer Beta version of the framework's OrderEntry App for PB2019R3 and PB2021 later today to SourceForge. A new "beta" version of the OE App was uploaded for PB2019R2 last night. This R2 beta is all about aligning the code for R3 and PB2021.  ;-)

HTH

Regards ... Chris

Hi Roland,

If there’s PB IDE installed on the machine, then pb.ini resides in the path of %localappdata%\Appeon\PowerBuilder 19.0.

If PB IDE is not installed on the machine, then pb.ini has to be put in the same folder as the .exe to take effect. It will not take effect if pb.ini is put in the runtime path or the search path or other paths.

Regarding the enhancement request of “add a set runtime option function” to take place of some settings in pb.ini, I think this is a very decent suggestion. I will submit this again as a new requirement to the Product Team. They will prioritize the implementation of requirements.

Regards,

Ken

Hi Roland,

I agree with you.

I used ProcMon to find out where the application is seaching for PB.INI:

First place is the application EXE directory.

If it doesn't find the file it seems it uses the PB.INI from C:\Users\[currentuser]\AppData\Local\Appeon\PowerBuilder 19.0. (Seems it takes this path from registry.)

I renamed the file to check if it is seaching at other places. But it seems not.

I think it would not be a good idea to look for pb.ini in system path. If an application would place its pb.ini anywhere it would be no guarantee that it would be found first. Maybe another applications places another pb.ini. First found - first servers may produce problems.

Of course, using a function to set an option would be the best way!

Regards,

René

Like you, I would LOVE to see a list of ALL of the runtime options, whether they're put in the INI file or set with a function.

Olan