ReportPro 2.x - MacroCompiler does not accept umlaut
Posted: Tue Jul 30, 2019 10:01 am
Dear fellow Vulcans and XSharp'ers!
I have a very strange problem regarding Vulcan.NET (3.0.303.0) and ReportPro 2.x (.NET as well). One of our customers' just got a new client and when the user starts a ReportPro Report (With RPT designer file), any variable which has an umlaut in the init expression - e.g. "Übertrag" - will show an ReportPro error "Invalid initial expression 'Übertrag'". The finished ReportPro preview/print document itself does not have any problems with umlaut characters, they all are displayed properly, so the problem is more annoying than dangerous.
The same issue happens when opening such a RPT file with the RP designer on the concerning client (Whereas there is no SetNatDLL call within ReportPro, at least none of which I'm aware of). When editing the concerning variable in the expression window, pressing the "Test" button will lead to a "There is an error within the expression" message.
The client itself is a german Win 10 with German-IT settings.
All other clients do not have this problem, the application components are equal. Our application has a SetNatDLL("German.DLL") "compatibility loading call" which was sufficient so far for the MacroCompiler to get along with all german special characters.
Does anyone have an idea what could be causing this issue or how to get this problem solved?
Best regards,
Bernhard
I have a very strange problem regarding Vulcan.NET (3.0.303.0) and ReportPro 2.x (.NET as well). One of our customers' just got a new client and when the user starts a ReportPro Report (With RPT designer file), any variable which has an umlaut in the init expression - e.g. "Übertrag" - will show an ReportPro error "Invalid initial expression 'Übertrag'". The finished ReportPro preview/print document itself does not have any problems with umlaut characters, they all are displayed properly, so the problem is more annoying than dangerous.
The same issue happens when opening such a RPT file with the RP designer on the concerning client (Whereas there is no SetNatDLL call within ReportPro, at least none of which I'm aware of). When editing the concerning variable in the expression window, pressing the "Test" button will lead to a "There is an error within the expression" message.
The client itself is a german Win 10 with German-IT settings.
All other clients do not have this problem, the application components are equal. Our application has a SetNatDLL("German.DLL") "compatibility loading call" which was sufficient so far for the MacroCompiler to get along with all german special characters.
Does anyone have an idea what could be causing this issue or how to get this problem solved?
Best regards,
Bernhard