Crystal Reports - Intermittent Parameter Problems with Viewer

Crystal Reports Viewer - Reports with Parameters Problem

I have --some-- workstations that get the following error when they try to view reports with parameters using the Crystal Viewer.  However, they are able to view reports that do not have parameters.

In a pinch, I was able to solve this by installing the entire Crystal Reports Dev Package.  However, this is not optimal.  What objects/dlls/references might I be missing that are causing this intermittent problem.

===================================
This document could not be opened. It does not appear to be a Crystal Report document. This document has the expected file extension (rpt.), but it seems to be corrupted. If this report used to work, try opening it with a different version of Crystal Reports and if that still does not work, please contact your administrator.
===================================
WEhaltAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MIKESoftware Solutions ConsultantCommented:
Did you change versions of Crystal by chance?

MikeV
0
WEhaltAuthor Commented:
Thank you for your response, but I actually finally got an answer from Crystal themselves.  It was quite involved, but here is an overview so that anyone searching this problem may be at least partially enlightened.

To get crystal to work on a deployed machine:
1.  Download the 'Merge Modules' from Crystal's website
2.  Configure same with your Crystal Dev License Number
     a.  To accomplish this you need a utility called Orca.exe
     b.  Once in Orca.exe, you open the license module
     c.   Enter your license in the PID... field
3.  Get ahold of Visual Studio 1.1 (that is just what Crystal recommended)
     a.  Open Visual Studio
     b.  Add the modules from #1
     c.  Build the project which creates an install file (.msi)
4.  Run the Crystal install on deployment machines before installing your program

I was left wondering how on earth I could have figured this out on my own, but it worked.

W
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic Classic

From novice to tech pro — start learning today.