I did some research and found out that the Crystal Reports Engine that must
be distributed with an application like Emerald to be able to print reports
is a single (large) file: CRPE.DLL (16-bit version) or CRPE32.DLL (32-bit
version).
There are other ways to do it, but it appears that Emerald uses this method
(or an Active-X method with the CRYSTL16.OCX or CRYSTL32.OCX file), because
I found the CRPE files on the server that Emerald is on, in the
/Winnt/system32 folder.
There are some other required runtime files, but they don't seem to be
directly related to the 5.0 issue.
(These are the files Emerald uses:
FILE DESCRIPTION
CRPE32.DLL Interface to the Crystal Report Engine
MSVCRT20.DLL Microsoft Foundation Class Runtime Library
CTL3D32.DLL* Version 2 of the 3 D control implementation
IMPLODE.DLL
* There is a different version of the 3D control DLL for Windows 95 and
Windows NT. Ensure you are using the correct version when distributing the
runtime files.)
MY QUESTION FOR DALE (OR ANY OTHERS) IS THIS:
Will replacing the CRPE32.DLL engine now on the Emerald server with the
CRPE32.DLL that I find on the Crystal Reports 5.0 server enable Emerald to
recognize Crystal Reports 5.0 reports?
Even if you don't know the answer to this, I can experiment and try it.
Just wondering -- will this replacement screw up anything else on my
system, so far as you know?
Thanks for your input,
Adam