>> Here's what you might want to try...in ccCrystalTools, check the references to the CrystalDecisions namespaces, and do the same for the test form. Are the references ok? You might want to try removing them, and then adding them back in. Let me know how that turns out.

The references are the same between ccCrystalTools and CrystalReportsMainForm (ie, the files are pointing to the same path), although the latter doesn't include CrystalDecisions.Windows.Forms (adding it didn't help). I tried removing and re-adding the Crystal references to each project. I really don't know enough to say whether or not the references are "okay." The path to CrystalDecisions.CrystalReports.Engine, for instance, is

C:\Program Files\Common Files\Crystal Decisions\1.1\Managed\CrystalDecisions.CrystalReports.Engine.dll

The files are actually at the location referenced. FWIW, I'm also seeing a ...\2.0\Managed\ folder. I tried replacing these files with still no success on the build. I don't have the VS 2005 Beta installed - I'm guessing this 2.0 folder was maybe installed with CR9 or a Crystal patch I think I installed.

>My only immediate guess is that while you have Crystal 9 installed...either the .NET managed code DLL assemblies weren't installed, or maybe they are installed but there's a problem finding them.

Doesn't appear this is the problem. I'm saying this because I have just received the Bischof book and the downloaded examples are working so far without issue. The references in that project are pointing to the same (1.1) location that was originally installed with your code.

Thanks for responding and enjoy your time away.