Java report tool FineReport Common Errors and solutions (2), javafinereport

Java report tool FineReport Common Errors and solutions (2), javafinereport

 

I hope that you can solve your own problems and solve them. Mark them to benefit yourself.

 

If any problem occurs, first search for the document, and then check whether du Niang is there, and then check whether there is a forum. If an error is reported, the log must be viewed. Below is a simple list of common problems that are mentioned in most documents.

 

1. No data set is returned:

Add set nocount on before the operation statement in the stored procedure or add this sentence before the data set exec calls the stored procedure. When set nocount is ON, no count is returned (indicating the number of rows affected by the Transact-SQL statement ). When set nocount is OFF, return the count. If some statements contained in the stored procedure do not return much actual data, this setting greatly reduces network traffic and significantly improves performance.

 

2. The template file is damaged, or the opening template does not respond:
The cpt template of FineReport is a set of labels enclosed by the source files made by the designer. As with the HTML structure, you can open it in a text editor. Some customers' templates may be relatively BT, or the high and low versions may be messy, or the DT is being operated, which leads to incomplete templates. Generally, an error is reported to indicate the error location.

3. The template cannot be found:
The template may not be found to see if it is a URL issue. If you write Chinese characters directly in the template, Some browsers will automatically transcode (remember chrome and sogou as if they are), and some will not, for example, IE.

4. java heapspace and stack overflow:
This is the question of DU Niang. The common cause is that the template is very complicated. It uses hundreds of fields, hundreds of SQL statements, and various nesting statements. Pay special attention to whether there is an endless loop. It may also be a problem on the server side. For example, if the maximum memory of tomcat is too small, the default 64 M is used.

5. There is a problem with the drop-down check box parameter in the dataset definition:
The Return Value of the drop-down check box control is an array by default, the string obtained by the parameter is not enclosed by quotation marks (you must manually add single quotation marks if you call a string-type parameter in the SQL statement defined by the dataset ). Multiple values are in. The SQL in statement parameter is a string array. Each value must contain single quotation marks. Therefore, to convert it, change the return value of the control to a string, and use the delimiter ','.

6. The local preview effect is different from that on the server:
First, check whether the jar package is correct. It may also be a problem after the platform is embedded.

7. The platform management forgets the password or fails to log in:
Report platform management has only one account, and the user name and password are stored in web-inf/resources/privilege. xml. Delete to reset.

8. Chinese Garbled text in the chart (box ):
This is often the case after oracle is installed in this Linux environment, because the box lacks Chinese fonts (Common English fonts should be available in various environments ). Install the corresponding Chinese font.
It is not uncommon for a large database to break down the font environment. The last time domino was installed in win7, many software fonts were involved, and the computer was restarted after the Chinese font of the system was reinstalled.

9. Chinese characters are garbled during dataset Preview (full question mark ):
Garbled characters can be found in several situations: one is a box, which is the reason for the font and cannot draw Chinese characters. One is the question mark. This is the encoding problem. For example, if the default encoding of the mysql database is latin1 and there is no Chinese encoding in the database, the database cannot parse Chinese characters. The solution is to change the encoding, for example, change the mysql encoding to utf8 or gbk. Note that the database includes the server code and client code. The specific database and table are also encoded, you only need to select the correct encoding when creating a database table (if not selected, the default encoding will be used ).