Crystal Reports Deployment Problem. (CRViewer.dll)

Using VB 6 (sp6)
Crystal Reports 8.5 (sp3)
and install shield 3.5 Express (sp4).

The VB program on my development machine, is pointing to a version of CRViewer.dll that is version 8.6.1.758 dated 8/27/2003.

When I do a build (using install shield) for the VB program I get an Old version of CRViewer.dll, Version 8.5.0.217 - Dated 2/3/2001 in the build.  

When I deploy the program using the build to a target machine, it fails to run the report, but the report runs fine on the development machine.
(The target machine gets the CRViewer.dll version 8.5.0.217, because
 that is what is in the deployment package.)

But I need to get Version 8.6.1.758 in the to build.

The problem is: I am using merge modules to get the right combination
of crystal report files into the build.

But I cannot find a merge module that will give me the version 8.6.1.758
of CRViewer.dll, which is what I want. I have downloaded the latest meger modules
from the Macrovision site.

I can manually add the files to the build (in install shield) and
not use the merge modules, but then I might not get the right combination of files I need.

Thanks in Advance,

Laurence
   
misdevelopersAsked:
Who is Participating?
 
GranModCommented:
Closed, 250 points refunded.
GranMod
The Experts Exchange
Community Support Moderator of all Ages
0
 
ptan218Commented:
Use the Package and Deployment tool from Visual Studio.

After the dependencies check, it will probably list the CRViewer.dll.

You can remove it by unchecking it in the Include Files screen and then ADD to select the correct version of your CRViewer.dll.
0
 
misdevelopersAuthor Commented:
I don't think I can do that. I have never used the package and deployment wizard,
and I don't know if it will do everything that we now get from Install Shield.

0
 
fostejoCommented:
misdevelopers,

I think you're on the right path wanting to stick the InstallShield packager - it creates MSIs, far exceeds the capabilities of the VB6 P&D Wizard and, importantly, as you already know, it also allows you to take advantage of Merge Modules.

As the CR DLLs/OCXs are generally downward compatiable, I suspect you should be ok using the CR9 Merge Module available from Business Objects at http://support.businessobjects.com/fix/merge_modules.asp (please ensure you carefully check exactly which Merge Module set you're downloading though)

The important thing is that you don't code your application to work with a very specific version of the CR DLLs (a *minimum* supported version makes sense of course) and, afterall, a.n.other application could at any time upgrade the CRViewer DLL and you'll obviously want your app to continue functioning!

cheers,


0
 
misdevelopersAuthor Commented:
I stuck with InstallShield, even though we paid for a support call and install Shield support couldn't solve the problem.
We can't go to Crystal reports 9 as that required programming changes.

What I did was to remove the crystal reports merge modules in the install shield build project.
I then had to go in one by one, and manully put in each crystal report file, where they are suppose to be on the target machine.

I took some time, but it worked, all of the proper crystal report files where install to the target machine, and the report ran fine.

Thanks for everyones suggestions.

Laurence


0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.