StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The Localize property you are referring to in the documentation and in the code-behind reports are for the <a href="http://helpcentral.componentone.com/nethelp/AR7Help/OnlineEn/?ReportTypes.html" rel="nofollow">code-based "Section Layout" Reports but won't work for XML-based "Page Layout" reports</a> (<em>if you look at the generated code for the report, you'll see that the designer is just generating a bunch of code to localize the report</em>).</p> <p>Since code-behind reports support custom code or you can add references to another DLL you can write a simple function to localize captions. There is <a href="http://www.codeproject.com/Articles/33355/Localization-of-SSRS-Reports" rel="nofollow">a good example of localizing this for .rdl reports here</a>, you can use exactly the same approach with the ActiveReports' .rdlx files. </p> <p>During that initial configuration of the report to be localizable you'll either have to manually change each static string to a <code>Code.LocalizedValue</code> call or maybe you could write a simple script to find each <a href="http://msdn.microsoft.com/en-us/library/ms155045%28v=sql.90%29.aspx" rel="nofollow">//Textbox/Value elements</a> and replace it with a similar call. A simple script with a combination of xpath and regex could do help you automate the initial configuration of the report. To localize something other than a Textbox Value in the report (e.g. report parameter, labels/bookmarks), you'll need to replace the text of a different element than the Textbox Value but the concept is the same. </p> <p>Of course, I am assuming you are localizing the static strings in your report. If you want to localize the values from the database then you'll have to do that differently (comment if you need help and I'll explain).</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload