Providing support for all E. Crane Computing products, including POWERGEN, PBSERVICE, HARPB, VERSIONEDIT, PBLRESCUE, and PBLEXPLORER.
You are not logged in.
Situation: our product's latest 2 versions are based on PB 11.5, while the previous 3 existing versions are still on PB 10.5
often developers make debugs in the latest version (trunk), which are then merged back to all relevant previous versions.
if the debug includes a change on a datawindow, the change always includes updated PB version in the definition: "release 10.5;" becomes "release 11.5;"
when later the build is done with PowerGen for PB 10.5, the process waits (infinitely) when encountering a version number which is higher than 10.5.
--> this should be avoidable; it would be much better to skip this datawindow and log an error instead.
Can this be done?
When I do this from the GUI I get an error dialog about the release level being incorrect.
Are you running from the GUI or the command line?
Regards,
Phil
we are running from command line (with option /Q)
The PowerBuilder DLL, called by PowerGen to regenerate the DataWindow is displaying the error message (bad). Will add to the enhancement list a feature to parse the DataWindow (from PowerGen) before it is regenerated. The the release level is incompatible we'll log an error and avoid calling the PB DLL.
Does that sound like an acceptable solution.
Regards,
Phil