Problems upgrading Crystal Reports

[CaptainCaveman]

I've a VB5 application which uses Crystal Reports 4.6 in it. I just upgraded to Crystal Reports 7, and compiled a new exe.

Unfortunately, if I run the exe on a machine that does not have CR7 installed on it and try to open the form that has the Crystal control on it, nothing actualy happens! The form doesn't load, no error is produced - nothing!

Any help much appreciated. Thanks

[LAURENS]

Did you reinstall your app (with the new components in it), that is, an entire new setup ?

Are you using the control or the object model ?
Did you convert the report layouts to CR 7 format ?

[CaptainCaveman]

I converted the report into CR7 format ok, and am using the control model.

I've created a proper installing program with the VB setup wizard and it works fine. Unfortunately the new application will be distributed via a network - rather than simply copy all the setup files the preferred option seems to be to add any additional dll's, ocx's, etc then register them if required. I could do with finding out which file(s) are actually causing the problem so that we only need to distribute it/them with this latest update.

I've created a dependancy file - the following files were updated to new versions:

da02535.tlb, dao350.dll, crpe32.dll, crpaig32.dll, crxlat32.dll, p2bbde.dll and p2bbnd.dll.

Presumably all of these wil be required, though I'll need to check a standard user's machine to see if any of them are there. Not sure which one is the culprit, assuming I'm on the right track.

[LAURENS]

Are you also distributing these ? (I'm sorry, i took them straight out of a setup.lst)

[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,55808,7.0.0.5
[email protected],$(AppPath),,$(Shared),6/21/99 5:00:00 PM,27136,0.0.0.0
[email protected],$(AppPath),,$(Shared),6/21/99 5:00:00 PM,38400,0.0.0.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,25088,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,56320,7.0.0.5
[email protected],$(AppPath),,$(Shared),6/21/99 5:00:00 PM,44544,0.0.0.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,126976,7.0.100.2
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,59392,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,19968,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,50688,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,17920,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,61952,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,14336,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,93184,7.0.0.16
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,143872,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,8192,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,10240,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,32256,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,37888,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,38400,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,18432,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,8704,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,171008,7.0.100.16
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,138240,7.0.100.1
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,140288,7.0.100.6
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,143360,7.0.100.1
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,234496,7.0.100.28
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,145408,7.0.100.2
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,50688,7.0.100.2
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,36352,7.0.100.2
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,199680,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,79872,7.0.100.2
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,59392,7.0.0.3
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,143360,7.0.100.0
[email protected],$(WinSysPath),,$(Shared),6/21/99 5:00:00 PM,60416,7.0.0.0

Are you sure craxdrt.dll registered well ? I had a similar problem. My app was distributed via SMS and all seemed to go well, but CR didn't do anything. It appeared that due to an updated virusscanner and an old version of mfc42.dll carxdrt.dll didn't register. I replaced mfc42.dll with the version that came with the vb setup, registered the new mfc42.dll and then registered carxdrt.dll. That worked for me. (Disabling the virusscan at setup might have done as well, come to think of it).

[Edited by LAURENS on 06-22-2000 at 07:57 AM]

[Kersey]

if your viewing .rpt files with the crystl32.ocx your VB-setup needs even more dll's :
msvcp50.dll !!!!( tricky bastard)
craxdrt.dll
crviewer.dll
crpe32.dll
sscsdk32.dll (charts)

[CaptainCaveman]

Thanks both for your help - I'll check up on those additional files. Do you know if they're only required with CR7? Our users have the application running and using CR4.6, so I'll need to upgrade/install any newer or new files.

[LAURENS]

4.6 also uses lots of u2 dll's. You need to install the new ones. Just check the date. The 4.6 dll's are from 1996. The 7.0 are from 1999. Did you get MR1 for CR7 by the way ? CR7 had ton's of bugs, most of which are repaired with MR1. You can order it for free at Seagate. There is no download because it's not a patch but a fully new installation.

Oh, i said I had problems registering crxlat32.dll. This should be craxdrt.dll. You probably won't need that one because I think you only need it when you use the object model instead of the control.



[Edited by LAURENS on 06-22-2000 at 08:02 AM]