For all those who asked, and those who are pulling their hair out after
getting "Could not open report file" messages, here is the list of CRW
files required for distribution (as per MSDN):

<snip>
   CRYSTAL.VBX       Crystal Custom Control file
   CRPE.DLL          Interface to the print engine.
   COMMDLG.DLL       Printer and file selection dialog box routines.
   CRXLATE.DLL       Only needed if your program uses ToWords() function.
 * PDIRJET.DLL       Crystal engine DLL.
 * PDBJET.DLL        Crystal engine DLL.
 * MSAJT110.DLL      Microsoft Access engine DLL.
 * MSAES110.DLL      Microsoft Access engine DLL.
** MSABC110.DLL      Microsoft Access engine DLL.
** CTL3D.DLL         Microsoft Access engine DLL.
   VB.INI            Visual Basic initialization file.
NOTES:
 * Files marked with one or two asterisks should be added to the list on
   page 582 in the "Visual Basic Version 3.0: Programmer's Guide."
** Files marked with two asterisks need to be added to the list in
   Appendix A of the "Crystal Reports for Visual Basic User's Manual."
Visual Basic's run-time dynamic link library must also be distributed with
any executable Visual Basic program:
   VBRUN300.DLL
<snip>

Thanks to The Microsoft Developers Network

-----------------------------------------------------------------

         Usenet Posting
-----------------------------------------------------------------

As a side note, you do not need to use the Crystal VBX in order to run or
modify your reports through VB. You can bypass it and use Crystal's Print
Engine (CRPE.DLL) directly. You also have much more flexibility and
control over your reports (especially if you are changing or setting a
lot of things on the fly). It will also eliminate one more VBX from your
project.

Dennis D.