janve

Because of this we work in this moment with RTF but it would be great if these problems could be solved.

Hi Sven, Thanks for your reaction. I will try to explain why I want to have the iReport compiler do this task for me… I notice that iReport checks the sql when you start building a report. When creating a sql-string in iReport, iReport checks which columns are available for building the report. When you you want to use a field in the report which is not available by sql, and you compile, the compiler raises an error message “field not foundâ€. I like this feature of iReport, because it prevents me to make mistakes. When compiling existing reports iReport doesn’t check anymore if the columns the reports want to use are really available. I can think of 3 reasons why it’s very convenient to have this check when compling with IReport: 1) It prevents me to make mistakes, some changes happens on the database and I'm not aware of all of them; 2) The error is discovered before the report is excecuted in production. I suppose that it’s good to discover errors In early stages, before to go to production; 3) To compile and check (by excecuting) all your reports manually is boring and can use some automation with Ant or Batchcompiler. It will be good if the compiler can do the check if the sql strings are still delivering the field which reports wants to use. Best regards, Jan van Engelen

Hi Sven, Thanks for your reaction. I will try to explain why I want to have the iReport compiler do this task for me… I notice that iReport checks the sql when you start building a report. When creating a sql-string in iReport, iReport checks which columns are available for building the report. When you you want to use a field in the report which is not available by sql, and you compile, the compiler raises an error message “field not foundâ€. I like this feature of iReport, because it prevents me to make mistakes. When compiling existing reports iReport doesn’t check anymore if the columns the reports want to use are really available. I can think of 3 reasons why it’s very convenient to have this check when compling with IReport: 1) It prevents me to make mistakes, some changes happens on the database and I'm not aware of all of them; 2) The error is discovered before the report is excecuted in production. I suppose that it’s good to discover errors In early stages, before to go to production; 3) To compile and check (by excecuting) all your reports manually is boring and can use some automation with Ant or Batchcompiler. It will be good if the compiler can do the check if the sql strings are still delivering the field which reports wants to use. Best regards, Jan van Engelen

Dear reader, I have the following problem: Description: I use a sql query as a datasource for a report. The report runs fine. Then I rename a column in a table/ view in the database where the sql query and the report makes use of. After this I Compile the report and everything looks fine. However when you execute the report you will get an error message that says that there is a ‘Unknown column name’. Questions: 1) Is there a possibility that when compiling the report (with ‘ANT’ or ‘Massive Compiler’) the compiler will do a “Read Fields†and checks in this way if the sql is still working? 2) Is there a way that if the sql is not working (anymore, because some change in the database) the compiler will give an error message? Background of problem: I started to have some problems with reports in my application. Having a check on the sql with "Read Fields" when compiling reports, prevents having reports in the application which doesn’t work because column names are not matching or the sql is not working. I will appreciate much if there is an answer to questions 1) and 2) Best regards, Jan van Engelen

Hi Lucian, The batch exporting sample shows that it can merge 3 (or more) reports to 1 pdf file. Every report section starts with pagenumber 1 in the pdf. Can you give me a clue if there a possibility to get a continuous pagenumbering in the pdf file? Best regards, Jan

Create a crosstab and go to the menu elementproperties. It shows a tab which is called hyperlinks. Is it possible to create a hyperlink on a crosstab element (for example on a column/row header or on a detailelement) ?

Hi Lucian, the best wishes for the new year! My excuses for uploading the wrong courier text. I hope you can try again using this "good_courier" file. It contains the char(10) en char(13). You can see for example that if you open the file in notepad the text is shown in 1 line, but if you open in wordpad it opens in many lines. Best regards, Jan [file name=good_courier.txt size=668]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/good_courier.txt[/file]

Char(13) = carriage return and sometimes there is a char(10) = linefeed

width: 350 pixels but can be other size too. additional info: The goal was: show some sql statements in pdf report and keep the original layout. If not sql becomes difficult to read. AWT doesn't recognize to start a newline in the courier text. It wraps up all the text. Itext pdf recognize that a new line starts but because the space calculated by AWT is to small the result is truncation. Regards, Jan

Lucian, Coming this far I want to ask you to make the next effort. I cannot think of another way.... To replicate the situation quickly: 1) Put the courier text in a database. In this case it was stored in Oracle with datatype varchar2(2000) 2) Get the field with the courier text with sql 3) Set the Font Name to "courier new" and the PDF Font Name to "courier new" 4) mark the "checkbox stretch with overflow" 5) run the report in jasperviewer and itextpdf to see that text in pdf is truncated [file name=courier_text.txt size=651]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/courier_text.txt[/file] If there is a better possibility to replicate the situation pls let me know.. Best regards, Jan

I tried but it's not possible. De characteristic of the courier string (with comma's, newlines, many spaces, "=" character) will not compile when putting it in a textfield without editing the text. In this way it's losing it's original layout. Best regards, Jan Post edited by: janve, at: 2007/12/20 18:44

Hi Lucian, thnx again for your time! I edited the file "default.jasperreports.properties" in the "jasperreports-1.3.1.jar" with winrar and set net.sf.jasperreports.export.pdf.force.linebreak.policy=true. It gives a slight difference in the itext-pdf (see picture, but the courier tekst still is truncated.. There is no use of tab characters in the courier text. size=390]http://www.jasperforge.org/components/com_joomlaboard/uploaded/images/itext_pdf___courier_linebreak_true.png

c) size=389]http://www.jasperforge.org/components/com_joomlaboard/uploaded/images/c__itext_pdf___courier-931fe2d5c5670b6459929cfa4fd56a4e.png

b) size=389]http://www.jasperforge.org/components/com_joomlaboard/uploaded/images/b__primopdf_pdf___courier.png

[file name=a__jasperviewer___courier.png size=21420]http://www.jasperforge.org/components/com_joomlaboard/uploaded/files/a__jasperviewer___courier.png[/file] Post edited by: janve, at: 2007/12/19 15:48