ASP.NET Page Print (20041117)
A system will definitely have a report or query, then it means to be printed, and how does the ASP.NET page implementation? Through my practice, it is as follows: 1. Crystal report advantages: powerful, flexible definition Report. Disadvantages: It is not easy to deploy (transplant is inconvenient, you need to retrieve components and enter licenets, etc.), implement cumbersome implementation: first establish a report (.rpt file) and put a CrystalReportViewer control on the page to be printed, before printing The report source is specified to page control. 2. Print page advantage: Simple and easy to use. Disadvantages: Page settings are not flexible. Implementation: Transfer parameters to the print page (preset report style), and display the data to print data, Then press "Print" directly in the toolbar. But by default, it has a header and footer when printing. If you want to take it off (of course, you can manually set, if the customer is willing), the program There are two ways to implement, but must be a client code implementation because if the server code is implemented, it will modify the server settings, as follows: a. Modify the registry
