Reporting Service is a report development tool provided by Microsoft integrated in Microsoft SQL Server. Since SQL Server 2000 is always used, Reporting Service 2000 is a natural choice. Reporting Service 2000 is the first version of Reporting Service, so there are still some bugs in it, and the usage is not very good. Below I will go through my own development process, make a basic arrangement and Related Countermeasures for the problems encountered.
1. the following error message is displayed, indicating that some GDI +, # TMP (temporary table name) does not exist.
This problem occurs when Reporting services preview reports and execute data sources, especially when the stored procedure using temporary tables is used as the data source.
Countermeasure: Ignore it because it can be viewed normally after being deployed on the server.
2. When the stored procedure is used as the data source, updating Fields sometimes clears all Fields.
Sometimes, when the stored procedure is used as the data source, open Fields and update fields. It is found that fields is empty.
Countermeasure: Open the data source editing interface, enter the Fields panel, and manually add the data source.
3. In a Reporting project, you cannot create folders, that is, you cannot classify reports by folders. You can only store all the reports in the root directory.
Countermeasure: there is no good solution.
4. When a stored procedure is used as a data source, the stored procedure using a temporary table cannot be referenced in the stored procedure; otherwise, an error occurs.
For example, if stored procedure A calls stored procedure B in process A and A temporary table exists in Stored Procedure B, the query analyzer performs everything normally, however, when A is used as the report storage process, you may encounter problems when querying data or browsing the report.
Countermeasure: copy the content of stored procedure B to process ).
5. garbled characters may occur when a Reporting Service report containing Chinese characters is exported to a pdf file. This problem cannot be solved in reporting service 2000.
To be continued...