>>I am glad to hear I am not alone at this point. I have been working in .Net for 2 1/2 years and have not had to print anything. However the current project would be significantly enhanced with PDF reports for download. At this point I have not even a clue as to where to begin.
>
>Sounds like a lot of us are in the same boat! <g>
>
>We decided to go with Sql Server Reporting Services (SSRS) ... the users can then tweak and create their own reports.Gotta have knowledgeable users of course. I haven't even looked at any of that, so I don't know anything about it. A lot of people use Crystal for their reporting ... another thing that I don't know how to do in .NET (I'd done Crystal in a previous life though). A developer on my team figured out how to do a Print Screen from .Net. It looks like complicated code, but this particular guy tends to over-complicate *everything*, so I bet his code can be simplified! <g>
>
>~~Bonnie

I spent some time researching doing reporting in .net with Crystal and SSRS. I did a comparison chart if you'd like it. It's not formatted to post here so I'd have to email it.

Both tools are very easy to use, but there are definite advantages/disadvantages to both.

At the time, our requirements were a little unusual. Initially, one of our requirements was to generate reports from entity classes that live in a separate assembly. That requirement has since changed. There was very little information out there on it, but I did get it working with SSRS and Crystal. Since Crystal is unmaged code, it requires a stub class in it's assembly to 'see' the entity classes in a separate assembly, but it will work then.