Skip to main content

CR9 to CR XI Upgrade

Since last couple years we have been using Crystal Reports 9 as our reporting tool with applications developed in VB6. Recently we deployed a new Staging server just to find out that we couldn't make CR 9 work on it. No matter how many DLLs we installed/uninstalled, the crystal report viewer would not load. I called up Business Objects Support, once again just to find out that they do not support CR 9 anymore.

I finally made the call to upgrade our reporting tool to Crystal Reports XI version. To all of you out there wanting to upgrade your CR9, I would suggest you upgrade to CR XI and CR 10 as I have heard (rumors) that support to CR 10 ends December 2007. I had to go around in a circle to get somebody to tell me a short and simple process to upgrade from CR 9 to CR XI. I got it and found it very useful so here I share it with you! If you find it useful let me know!

What you will need:
Crystal Reports XI, Developer Edition (to develop and integrate with VB6 / .NET application)
VB6 environment
EmptyInstaller.msi (obtain this from Business Objects customer service or email me and I can provide one - it is 56 mb)

What to do:
1. Install Crystal Reports XI, Developer Edition in your development environment.
2. Open your existing reports and re-save them with the same name with CR XI.
3. In your applications, include a reference to 'Crystal Reports ActiveX Designer Runtime Library 11.0'
4. In your applications, add 'Crystal ActiveX Report Viewer Library 11' control

Ready to Roll!

How to Deploy:
1. Install EmptyInstaller.msi on your deployment server (doing so will get you all the required DLLs and register them properly)
2. Deploy your Application(s) and report(s)

You are all set to use the CR XI!!

Note: For more pro help, refer to the documents on http://www.businessobjects.com

Comments

The Popular Ones

Using SQL To Calculate XIRR (Internal Rate of Return)

Thanks to binaryworld.net , I was finally able to get a sql way to calculate XIRR. After 2 long hours of search I found this site and the logic as well as the code works perfectly well! XIRR is a function in excel that calculates Internal Rate of Return based on payments/income over a period of time. Without further ado, here is the code (a slightly modified version from BinaryWorld.net. Happy XIRRing! -- First, CREATE XIRR Table to store values CREATE TABLE XIRRTempData( amt float, dt datetime, guid varchar(128) ) go create function dbo.XIRR( @d datetime, @GUID varchar(128) ) returns decimal(18,10) as begin /* USAGE: select @IRR = dbo.xirr(null, guid) select @IRR IRR, @IRR * 100 'IRR %' Note: Leave the first parameter (date) null if you wish to see the XIRR calculated as of the maximum date in the dataset provided else provide a specific date to see the XIRR calculated as the given date. Created By: Ankeet Shah Created On: 7/16/2008 */ IF @d is null SELECT @d = max(d) from Inc

Alternating Row Background Color For SSRS Matrix (Pivot Table)

I had a tough time to apply alternate row colors to a SSRS Matrix and finally figured out! Without further ado, here it is... Assume you have a matrix with more than 1, lets say 2 row groupings; RG1 and RG2. 1. Right-click on RG2 (innermost row group), and select "Insert Group"; for simplicity call it "RowColorGroup" 2. In the "Group On" section, add some constant value - for example ="" or ="ankeet" etc... you get the idea! 3. Select the newly created group "RowColorGroup" and enter the following in its "Value" property: =iif(RunningValue(Fields!RG1.Value & Fields!RG2.Value,CountDistinct,Nothing) Mod 2, "LightSteelBlue", "White") 4. Select the "BackgroundColor" property of "RowColorGroup" and enter "=Value" 5. Set the width of "RowColorGroup" to 0pt and "CanGrow" to false 6. Select the data cell(s) and set their "BackgroundColor" pro

cannot create a column accessor for OLE DB provider "ibmdasql" for linked server

I have a linked server from Microsoft SQL 2008 to a DB2 server. Today when I tried to run a SELECT statement based on the linked server, I hit this error, "cannot create a column accessor for OLE DB provider "ibmdasql" for linked server". Earlier in the day, we had restarted the SQL Server Service. Running the following script on the 'affected' sql server should fix the issue. USE [master] GO SET ANSI_NULLS ON GO SET QUOTED_IDENTIFIER ON GO CREATE PROC [dbo].[usp_enum_oledb_providers] AS exec sp_enum_oledb_providers GO sp_procoption 'usp_enum_oledb_providers', 'startup', 1 Restart the sql server service after running above script.