Unfortunately, I am getting error messages saying that some important DLLs
are missing, etc.

My problem is I don't KNOW which DLLs, and possibly OCX (I am using the
CRViewer), must be included.  I tried looking through the documentation I
had, but didn't find it.  And I tried looking on Seagate's web site, with no
success.

Bottom line: What DLLs and OCXs need to be distributed with a VB
application, which makes use or the RDC in a Visual Basic 6 Enterprise
Edition application, running against a SQL Server 2000 database?

Rod

You do not want to have the OCX checked when using the RDC, it causes
conflicts in your installation package and the dependancies.

For a basic VB app using the RDC you would have the following Crystal items
checked in References:
Crystal Report Viewer Control
Crystal Reports 8(or 8.5) ActiveX Designer Runtime Library
-any time you add a report to the RDC Crystal automatically taggs the CR
8(8.5) AX Designer Design and Runtime Library. You should remember to remove
this reference prior to creating your installation package as it will
conflict with the CR Runtime Library (craxdrt.dll).

You should NOT have the Crystal32.ocx tagged in Components when using the
RDC; remove it if you do. The  Crystal Report Viewer Control should be
present if you want the ability to preview your reports. I believe the RDC
adds this automatically when you add a report to the project (at least it
must when it asks whether you want to add a form for viewing the report and
you answer YES).

In your installation package you need to include the following DLL's as
dependancies for the craxdrt.dll (if you have not found this out already):
MFC42.DLL
MSVCP60.DLL
MSVCIRT.DLL
if using a DSN/FDSN include P2SODBC.DLL
if you wish to have Export capabilities you must include the u2*.dll file
for whatever export media you wish to use.
For PDF export you must include CRXF_PDF.DLL.
For Rich Text export you must include CRXF_RTF.DLL.
For export capability to work you must include EXPORTMODELLER.DLL (at least
in version 8.5, I can't remember whether I had to do so in 8).
CRTSLV.dll is a dependancy of a necessary file, I just can't remember which.
If you try NOT to include it I guess you can find out which requires this
file.

ATL.dll is a dependancy of both the EXPORTMODELLER and CRTSLV. On my Win2k
machine the ATL.dll uses Unicode, which Win98 could not register. I finally
found a copy of an ATL.dll on disc 2 of the Developer's Studio that listed
itself as being in ANSI format (ver 3.0.8168.0 if it comes up). So far I hav
e only installed my applications on Win98/NT4 machines, in both cases using
the ANSI version of ATL without issue.
It's been a while since I wrestled with this issue myself, so I may have
missed something but believe this covers the bulk of Installation Package
issues.

Oliver