Report Builder Issue

T

tony82

New Member
Dear friends,

I am using openEdge 10.1C on windows XP and i have a problem in report builder.
In fact when i try to run report builder (prorb32.exe) the following error message appears:
"Unable to read header information from convmapfile C:\Progress\OpenEdge\Convmap.cp"
If somebody can help me to solve this problem i'll be very thankfull.

thanks in advance,
 
The convmap.cp file used to convert characters from one code page to another. It contains the mapping tables. AFAIK it comes into play every time a conversion is needed ( for example you database uses code page UTF-8 and you client uses code page iso8859-1 ).

I would guess that this is a result of a PROPATH or PATH issue.

Did you verify that the file exists in the location the error messages indicates?


HTH, RealHeavyDude.
 
My friend,

Progress is installed under C:\Progress\OpenEdge
In Registry Editor : Progress -->10.1C --> Startup : PROCFG value is "C:\Progress\OpenEdge\bin\Progress.cfg" and PROCONV value is "C:\Progress\OpenEdge\bin\Convmap.cp"
And the file "Convmap.cp" is found under C:\Progress\OpenEdge.

Regards,
 
The settings in the registry are not necessarily picked up by Progress. There is a progress.ini located in the bin directory beneath your installation directory. During installation the contents of this file gets written into the Windows registry ( AFAIK it is the ini2reg executable that does that ). Each client uses that ini settings - if you don't specify anything than the Progress settings from the registry are taken. With the -basekey "INI" parameter you force the client to read the progress.ini file from the file system ( the first occurrence in the PROPATH will take precedence ). With the -ininame parameter you can specify a different ini, for example myini.ini. This way you can have you application specific ini settings in a file that is deployed as part of your application and you may chose to load into the Windows registry or use the file from the file system in supplying the parameters -basekey and -ininame accordingly.

Why I am explaining that: The Path in your Windows registry to your conmvap.cp is different than it's actual location ...


HTH, RealHeavyDude.
 
You must log in or register to reply here.
Back
Top