Questions and Solutions of Crystal Reports under VS.NET
Questions and solve the problem of crystal reports under VS.NET 2003-03-27 · · Shang Pure ·· Yesky 1. Load the report Times wrong, finally finished the procedure, the report is tested in the development of machines, To install the installation project, generate Huan Xing Chong to get the client to test, dizzy, report an error (as shown in Figure 1), how can it be carefully checked out the program code, there is no error, it seems that the problem The report is released. Figure 1 After a bitter, finally found the problem. The crystal report needs to include the following three components when the project is released: Report (* .msm) Running (* .msm) Running (* .msm) These module files are in C: / Program Files / Common Files In the / merge modules / directory, don't worry, let me say slowly. 1. Report (* .rpt) The crystal report file created when programmed, this is very simple, you won't find it, haha. 2, module (* .msm) Managed.msm This module contains the management module of Cr for VS .NET, such as Crystaldecisions, CrystalReports.EnGine.dll, Crystaldecisions.Web.dll, and Crystaldecisions.Windows.Forms.dll. ...... Managed_chs.msm is the Chinese version of the module. Database_access.msm This module contains a database of databases, coupled to different databases, exports documents and chart components in RTF and HTML formats. Database_access_chs.msm is the Chinese version of this module. RegWIZ.MSM registration information module, it is very important to enter the registration serial number of the crystal report in this module, if not filling, it cannot be passed, as shown in Figure 2. Figure 2 3, .. Running library (* .msm) If the report file uses the ADO.NET Data Dataset object, the VC_CRT.MSM and VC_STL.MSM modules must also be included in the installation project. And the "Module Retargetable Folder" item of the file installation properties of these two modules must be modified to become a system directory, as shown in Figure 3. Figure 3 Now, we know the answer, in the vs.net installation project, the system detected by the system only DOTNETFXREDIST_X86_CHS.MSM and Managed.MSM these two modules, and other modules we need to manually join. 1. In the Solution Explorer, right-click the installation item selection "Add" -> "merge module (m)", as shown in Figure 4. Figure 4 2, in the Add Module dialog form, select Managed_chs.msm, Database_CHS, RegWiz, VC_CRT.MSM, and VC_STL.MSM modules, as shown in Figure 5. Figure 5 3, regenerating the installation item, no problem, only the generated installer is 7, eight megabytes.
