I agree that the best approach would be an uninstall of .NET and a full installation. Make sure all registry entries have been removed and any files deleted that relate to the .NET install. Visual Studio .NET is very picky about the order of how installations are done and something may have occured out of order. Many people find this out when installing ASP.NET and IIS. See if that fixes your problem.

>Hi Cathi,
>
>I updated my print driver in windows.
>
>Now my program won't even load the report as the ReportSource for the report viewer.
>And now my VS.NET itself bombs(goes to a CLR debugger option) whenever I add a new CR item in the project manager ... even in different / new projects. And VS.NET now bombs when I edit previously saved reports ... at various times and places. It's just basically hosed, and I am considering a reinstall of .NET on my machine.
>
>I am ready to flush CR.NET down the toilet, and go buy a third-pary reporting tool. CR is the only thing in .NET that I have had a problem with.
>
>Thanks for the help, any suggestions are welcome, including and third-party suggestions for desktop and web printing from .NET.
>
>Ken