- Troy Cowan
- PowerBuilder
- Wednesday, 22 May 2024 04:54 PM UTC
I recently ran into an issue when moving from one build server to another - paths were different and it turns out there was a "hidden" hard coded path in the files that I wasn't aware of at first.
The .gen file specified a hard coded $PBRPath and the contents of the .pbr specified a hard coded path to the location of a .pbl.
I fixed all the hard coded paths and am building, but in doing so I have become quite confused about why we have this .pbr in the first place. The contents of the .pbr were simply:
E:\BRMD\Build\BBR\libraries\driver.pbl(d_scheds_to_run)
From what I gather, this type of thing is necessary if a datawindow is not in a pbl. However, as best I can tell (which pretty much means just looking in the .pbl in the PowerBuilder IDE), d_scheds_to_run is there inside of driver.pbl.
Therefore, it looked to me like this .pbr file was probably not necessary. But when I removed the line in the .gen file that specified the .pbr location, the application stopped working as expected. In the code where it attempted to run Retrieve on a d_scheds_to_run object it returned a -1. So I guess this .pbr really is necessary but for the life of me I don't know why.
Any advice would be great.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.