E. Crane Computing Support Forum

GabrielG

Guest

Re: Path

Hi,

I have a question/problem.

In one of my PBLs I have the application object ancestor defined. On it I defined several Instance variables whose values are retrieved
from a configuratiion file (an INI file),  As follows:

                       
*   C:\Dev_201\WorkPBLs\Main\Main.PBL   

*   Main.PBL contains object n_cst_rmc_appmanager.

*   n_cst_rmc_appmanager has the following instance variables defined:

                    CONSTANT string BUILD_INI_FILE = 'RSS05BUILD.INI'

                    PRIVATE int ii_increment_buildID = SetProfileString( BUILD_INI_FILE, 'settings', 'BuildID', &
                                                string( integer( ProfileString( BUILD_INI_FILE, 'settings', 'NextBuildID', '0' ) ) ) )

                    PRIVATE int ii_increment_nextbuildID = SetProfileString( BUILD_INI_FILE, 'settings', 'NextBuildID', &
                                                string( integer( ProfileString( BUILD_INI_FILE, 'settings', 'NextBuildID', '0' ) ) + 1 ) )

                    PRIVATE int ii_increment_date = SetProfileString( BUILD_INI_FILE, 'settings', 'LastUpdated', &
                                                string( Today(), 'Mmmm dd, yyyy') + ' at ' + string ( Now(), 'hh:mm AM/PM' ) )

I am using ABSOLUTE paths for compiling.

The problem I'm running into is that no matter where I place the RSS05BUILD.INI file PowerGen doesn't seem to find it.
I tried placing it in the Main folder together with the PBL, the Application folder, the WorkSpace folder, C:\ and C:Windows (the latter are are on the PATH variable).

I'm running on Windows XP SP2.
Powerbuilder 8.0.3.
PowerGen Professional 6.0.0.21 for Powerbuilder 8.

What am I doing wrong?
Or, am I missing a patch or something like that? 

Thanks for your help.

I figured it out .. thx.
     

Phil

Guest

Re: Path

Hi Gabriel,

What was it that you figured out about this?

Regards,

Phil

GabrielG

Guest

Re: Path

Phil,

sorry for the delay I edited my posting and didn't check back until now.

As you can see we have instance variables whose value is calculated dynamically.

The process we used to create the PBDs and the EXE is to take the PB objects source code and construct all the PBL libraries from scratch; the next step was create the PBDs and the EXE in two steps.

The way it was setup was to run Powergen in two separate steps one to create the PBDs (/P) and another step (/E) to create the EXE as follows:

C:\Program Files\E. Crane Computing\PowerGen Professional\Pwrgn8.exe
        /D /P=TheProjectFIle  /G=TheLogFIle /S

C:\Program Files\E. Crane Computing\PowerGen Professional\Pwrgn8.exe
       /D  /E=ThePRojectFile /A=TheAppObjName /G=TheLogFIle /S

but this way the dynamic instance variables are NOT evaluated by PowerGen.

The process was changed to run just one step (/A) as follows:

C:\Program Files\E. Crane Computing\PowerGen Professional\Pwrgn8.exe
       /D  /A=TheProjectFile /G=TheLogFIle  /S

This way the dynamic variables are evaluated and correctly.

The problem is not that Powergen doesn't find the INI file to evaluate the variables or that it doesn't look at the PATH environment variable to find the INI file.

The problem is the PG does not evaluate the variables when we use /P and /E. It does when we use /A.

Gabriel

   

Phil

Guest

Re: Path

Hi Gabriel,

I believe the problem is the /P and /E commands don't regenerate the objects, while the /A command does.

Regards,

Phil