Packaging CR7 problem

[CSalam]

Could somebody out there please help me. I'm beginning to run out of sanity here. I've been trying to package my CR (external RPT files, ver7) with my VB6 app for many days, and up to now I'm still back to square one. (I think my Drive Image is beginning to complain for overuse).

I've tried to include all the files that I thought needed by CR - to no avail. I even followed Seagate’s KB to the letter – to no avail. I keep getting this error:

Runtime error 339
Component CRYSTL32.OCX or one of its dependencies not correctly registered: a file is missing or invalid.

I really don’t get it. I thought everything is handled by VB’s P&DWizard, then how come I keep getting this message?

Then I checked Seagate's KB and followed the advise to register manually the file. But that, too, didn't help.

Seagate Crystal Report is such a great tool for creating reports but darn it's too hard to package and deploy. Please, tell me what to do. Please, please, please, please, please. I would really appreciate your help at this point in time.

 

[emcevoy]

Hi there.

Not sure why but for some reason the package and deployment wizard does miss some of the dlls needed to run the reports.
What version of Crystal are you using?
Do you get it telling you about any of the files that are missing?
When you manually registered the ocx, did it succeed?

One thing you can do is to try using the dsx or the modules tools that will let you find out what all dlls are needed and then you can manually send them in. If you don't have it on your system, it is located on the Crystal CD under tools folder.

it could also depend on the verson of crystal that you are using is also what could be the issue as some versions are in need of other files to be registered. it could be just something wrong with the dependancy file also, but we can leave that till last thought.

I know I have more questions than help at this moment, but I might be able to help further with the answers as I have seen this before.



E. McEvoy
Crystal Reports Consultant

http://www.pacificridgesolutions.com

 

[emcevoy]

Hi there.

Not sure why but for some reason the package and deployment wizard does miss some of the dlls needed to run the reports.
What version of Crystal are you using the Maintenance release?
Do you get it telling you about any of the files that are missing?
When you manually registered the ocx, did it succeed?

One thing you can do is to try using the dsx or the modules tools that will let you find out what all dlls are needed and then you can manually send them in. If you don't have it on your system, it is located on the Crystal CD under tools folder.

it could also depend on the verson of crystal that you are using is also what could be the issue as some versions are in need of other files to be registered. it could be just something wrong with the dependancy file also, but we can leave that till last thought.

I know I have more questions than help at this moment, but I might be able to help further with the answers as I have seen this before.



E. McEvoy
Crystal Reports Consultant

http://www.pacificridgesolutions.com