Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help! Can't display CR10 report in VB6 after upgrade from 8.0

Status
Not open for further replies.

lucyv

Programmer
Mar 11, 2002
152
US
I have a VB 6.0 application that uses Crystal Reports 8.0 to display reports from a directory below my application (i.e. "c:\myapp\reports\report1.rpt"). CR 8 has worked great for me for the past few years, but now our users are having problems exporting the reports from the crviewer to the latest version of MS Word & Excel.

I recently purchased CR 10 as the fix to my export problem. After modifying my app to work for CR 10 (switching the crview.dll and craxdrt.dll references) I was able to display the reports from my application.

However, when I packaged and deployed my application to another computer, one that already used CR 8.0, the viewer develops an error: -2147206429; Invalid TLF Record.

This error occurs when I try to try to open the report and set the refernce to the CRReport variable:
Code:
Set CRReport = CRApplication.OpenReport(App.Path & "\Reports\" & ReportName)

Does anyone know why this is happening? Do I have to install other file references besides crview.dll and craxdrt.dll? I can send more code if you need me to.

Thanks in advance.
 
I meant to type crviewer.dll instead of crview.dll.

I apologize for the typo

 
You'll need to create a new setup package to load the CR 10 .dlls onto the client machines. The easiest way to do that is to use the merge modules from Business Objects to build an installer (with Wise Installer, Visual Studio Installer, etc):

Here's a decent whitepaper on the different ways to deploy a CR 10 application:

-dave
 
Thanks vidru,

After looking at the rdc10_deployment whitepaper it seems that there are two merge files I need for my scenario; reportengine.msm and runtime.msm.

The whitepaper says I need some core runtime files including Crqe.dll, Ufmanager.dll, Craxdrt.dll, and Crviewer.dll. However, when I looked into the merge modules only the reportengine.msm has the Crqe.dll and Ufmanager.dll files. The other merge module, runtime.msm, has the Craxdrt.dll and Crviewer.dll files.

Is it save to assume that I will have to install both merge modules for my application to work correctly?

Thanks for all your help.
 
Yes, just include both of them when you build the package, and I believe you need to include the license.msm module as well.

-dave
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top