There are many reports in our system, which can be divided into REPORT and FORM, which is reported and documents. There are some standards in this middle, and some are customized for customers. The development of the report can be roughly divided into two parts: the query interface and the report interface. I do Form. It is a simple query interface relative to Report. We use the entire system Framework, here is not more. The report interface uses JsperReport's architecture and API, use IREPORT when making interfaces, all of which are open source free software I have made mistakes when Igo, can be divided into the following cases:
1. People with errors or write demands have entered the need for demand, although I have seen it seriously before doing and ask the analyst to explain, but this problem is still often there. There is no effective way to avoid this problem 2. The understanding of the system and is not enough to understand the business. Some problems have not given attention when coding. For example, Vessel and Voyage are divided into baound and Outbound, There is a logical error when Coding, and I can't find it. 3. Due to insufficient understanding of the system, it will cost more time when making test cases or test data, and often there will be omissions. From a person, everyone should have enough understanding of the system, but if the test data is prepared by QA, the developer is not to save some time, and this test case can be used after QA. Of course, this is only the development of the report. 4. Negotitude, this is the mistake of everyone. But I think it is necessary to effectively avoid errors, or reduce the error rate, which is actually applicable in any work, but because of the person's own Inertness is often unable to summarize. In fact, writing blog has such a role. It can be derived from history. It will effectively precipitate experience in order to get the gains, and it is not a dog-raising corn.
Then let's talk about technical issues. I have also done a statement before summing up the practice of the report. When doing a group company's financial statements, use SQL Server as a database, wrote some stored procedures for generating report data, this program is not known. We have written some clients with VB and ASP, and the client written by VB is mainly to deal with some reports, such as account settings, corporate settings, etc., can manually process some automatic generated reports, data acquisition Use a tool for data mining, nothing to know. Mainly written by ASP is the presentation of the report. In order to improve the speed of the report (the speed will be very slow, the speed is very slow, and the server is occupied), we have designed configurable dynamic queries, configured in the front desk Query conditions, generate a corresponding stored procedure, then place the query result in a temporary table so that you can directly look at the results of the query, or regenerate query data by the stored procedure. In fact, it is also equivalent to a cache function, otherwise all reports are in real time, the server will be overwhelmed. The front desk shows the report written on the ASP page. First, take the data to generate a unified format XML file, then write a javascript to resolve the XML file, then pass Microsoft's control, it seems to be one of the web component, parsing XML , Show the data. The advantage of this control is that the style of adjustment of the report can be dynamically modulated, for example, the ranks, rearrangement, and support summary, etc. The user will see a very comfortable interface on the interface, of course this is related to the browser.
In fact, the practice of the report, whether it is from design or realization, there is already a mature program, but this is still a very headache problem in the work, and where is it? Is it still lacking effective finishing of resources. Write like this today, tired!
