Deploying Crystal Reports using C# .Net 2003

Got rid of Crystal Reports deployment problem
This one was toughf, The crystal reports deployment problem was bugging me for last 3-4 days, finally solved the problem.

Few things to be rememberd while deploying crystal reports

1) Merge modules required are present in C:\Program files\commom files\merge moduledirectory
2)Following things to be added while deploying the application.1. Reports i.e. .rpt files2. CR Merge modules3. Dependancies
3)Merge modules to be added for VS2002 and bundeled CR are1. managed.msm2. Database_Access.msm3. Database_Access_enu.msm4. RegWiz.msmWhen RegWiz.msm is added it exposes licence key property which accepts key code
I got key codeRegistration number is 8013366187
Key Code: Your non-expiring code is AAP50-GS00008-1DW00JAProcedure for deploying with CRDeploying a Windows Application The following procedures assume that you already have a Windows application ready for deployment.To deploy a Windows application using the merge modules:

1. In VS .NET, open your Windows application and go to the View menu and select Solution Explorer. Right-click your Windows application solution and from the pop up menu, select Add then click New Project.

2. The Add New Project dialog box appears. Select Setup and Deployment Projects in the left pane and select Setup Project in the right pane. Click OK.

3. In the Solution Explorer, right-click the Windows application and select Add then click Project Output…

4. The Add Project Output Group dialog box appears. Select Primary Output to be added to your Setup project. When the Primary Output is added to the project, some detected dependencies will be added. • If you are using the bundled version of CR 9, add: managed.msm • If you are using the full version of CR 9, exclude: dotnetfxredist_x86_enu.msm and dotnetcrystalreports.msm In both cases, the dotnetfxredist_x86_enu.msm and dotnetfxredist_x86_enu.msm dependencies should be excluded if it is not already. NOTE If you are using the full version of CR 9: The dotnetcrystalreports.msm and dotnetfxredist_x86_enu.msm should be excluded because it will conflict with components in the other merge modules. Right-click on this item in the Solution Explorer and select Exclude.

5. In the Solution Explorer, right-click the WebSetup project and select Add then click Merge Module…

6. The Add Modules dialog box appears. Select the appropriate merge modules (see section above titled Crystal Reports Merge Modules) and add them to your project. Click OK.NOTE If you deploy a Windows application that uses an ADO.NET Dataset, you also need to include the two additional merge modules listed in the Runtime section above.

7. From your Setup project, select the licensing merge module to display the properties.

8. Expand the MergeModuleProperties and enter a valid license key the in License Key Properties box. The license key is the 19-digit alphanumeric string you receive when registering Crystal Reports. Please note that this is not the 10-digit registration number. This is mandatory whenever you deploy a Crystal Reports for Visual Studio .NET application. NOTE A license key will be given to you once you have registered Crystal Reports for Visual Studio .NET. You can also find the license key by opening VS .NET and going to the Help menu and selecting About…. Under the 'Installed application list' is the license key for Crystal Reports for Visual Studio .NET.

9. To build your Setup project, highlight and right-click your deployment package (setup1) in the Solution Explorer, and select Build. You are now ready to deploy your Windows application.

That's all foks.......Crystal Reports provide gr8 functionality but some times thay give vary complex problems...
You can post ur problem I will try to solve them