german special characters

[JoeintheBox]

Hi there, problem nb. 2 The same environment like in the "newest data" question. Sending text-strings to the report works with all of th special characters like "%" ">" and so on (via encoding in the "%XX"-format). If I try to send german special characters like "Ü" "ö" and so on - I retrieve an error from CE. What to do?

 

[Bobimann]

You want sending a Parameter whit "Ä,Ü,Ö" or you have this letters in the Databse?
If you use the Database which data source do you use (ODBC) ? if you ODBC use you must aktivate in the driver OEM.

I Hope that Help.

 

[JoeintheBox]

thx Bobimann, and sorry for my bad description of the problem...
better now:
im calling the report via

viewrpt.cwr?init=actx&id=<anyID>&apstoken=&quot; + Request.Cookies.Item(&quot;ePortfolio_logontoken&quot + &quot;&prompex-TEST=&quot;&quot;Paramstring%20for%20testing&quot;&quot; ... this works fine.

Replacing this stuff by &quot;&quot;german%20character%20öäü&quot;&quot; leeds to the error ... I only want to display this parameter in the report - not want to use it in a selection formula. Submitting the parameter in CR makes no problems ...

kindly regards
JoeInTheBox

 

[Naith]

Joe,

If you only want to display the umlaut and not have it affect the selection, then it isn't clear why you are trying to send the german character in your promptex.

Surely you should continue to send the regular sans-umlaut letters in the promptex string and use a formula like:

If {?Parameter} = 'Uber' then 'Über'
Else {?Parameter}

to exchange the promptex value with an umlaut. Promptexes directly affect the selection criteria.

I don't know if I've misunderstood your problem, but if I have please set me straight.

All the best,

Naith

 

[JoeintheBox]

@Naith: thx for the hint. I've build a user-friendly intranet application to store parameters, check for them consistence before applying to the long running reports. Users wish was to dynamical change the headlines and footnotes of the reports - I use parameters for this stuff, don't know another way...
Using your idea would be heavy stuff: User types in the html-form &quot;Über&quot; - then I've to change it in some &quot;Meta-Letters&quot; like &quot;XUeber&quot; and in the report back to &quot;Über&quot; ...
If I don't found another solution, I'll do so - but its not nice :-(

thx
Joe