
Migrating from Crystal Reports 4.6 to 5.0 Professional.
Yeowza!! That's a fair amount of work you suggest doing. We did the
following:
1) Removed the control from all forms in the project.
2) Removed the Reference from the Project file.
3) Added the new reference to the Project file.
4) Added the controls back.
This seems to work, sort of. What we're find happening now is whenever we
get into the project now, within VB, it complains about the Crystal Reports
control being out of date and asks if we want to upgrade to version 4.6 of
Crystal Reports, which of course is ludicrous as we're at 5.0 of CR.
Quote:
> You should certainly make sure that all forms containing the CR OCX
> are saved as *text* prior to upgrade. If saved as text, there will be
> no problem with using a later version of the OCX - this is described
> in the CR "readme" help with 5.0.
> But that's not all - there are problems in installing CR5 if it is to
> co-exist with the feature-limited version bundled with VB. VB5 at least
> gets OCX versions wrong and has problems in registering the OCX and/or
> .tlb and/or .oca files. I would recommend you completely remove your
> current VB/CR combination. Then custom reinstall VB choosing NOT to take
> its version of CR. Finally, install your standalone CR5 Pro.
> If running on a network (you have 5 licences) you might consider
installing
> CR centrally on the server and then doing "workstation" installs.
> --
> Les Schmalzbach
> (remove nospam- to reply).