>>>>Hi all, I have the task to create some reports for an existant C# module, i need to know if is it better to use Internal report viewer instead Crystal Reports? Please let me know.
>>>
>>>I just sent you an email with a table I put together comparing the two. The email also lists a couple of the links I used to gather the information. Some of the information in the table is based on those links, and some is based on my testing. I would have posted it here, but I don't have time right now to format the table for text display.
>>>
>>>Note that if html rendering or rounded rectangles are important to you, you will probably need to go with Crystal. HTML rendering is supported in the SQL Server 2008 schema, but not 2005. The 2008 Schema is used in the latest SQL Server 2008 report server. Support to display HTML markup is not in the reportviewer controls in local mode yet but according to MSFT, it is in the works (hopefully a spring release).
>>>
>>>Rounded rectangles can only be created in SSRS by using images and I havern't heard any plans to add that feature to SSRS in the near future (although I have seen it requested on MSDN numerous times).
>>>
>>>Other than what I wrote above, more information on the two is in the table I emailed you. I just added the little bit about rounded rectangles and html markup support here in order to expand on what is in the table. The table doesn't go into detail on those two items. Hope it helps you in your decision.
>>>
>>>Oh, one other thing. If you work with entity classes (for your data source), and those classes exist in a separate assembly, Crystal is not managed code so there is a trick to see those classes in design mode in Crystal. It is not a problem with SSRS (SSRS will see the entity props and pull the data when you run the report. You will have the props available in designtime to create the report), but with Crystal in order to 'see' the entities in design mode and in runtime mode, you have to create a shell class in the same assembly as the reports for each entity which is derived from the entity class and just simply call the base. Then Crystal can 'see' the entity props in the entity class. That is only an issue if you don't create your reports working with the data and a connection, but use a multi-tiered approach instead which utilizes entity or data classes. Also, if you work with entity classes and not with tables in Crystal, then you have to set up your relationship and create your source as needed because you will not be able to use the database relationship wizard in crystal in designmode with entity classes.
>>>
>>>
>>>Tracy
>>
>>Hi Tracy,
>>
>>Can you please send it to me as well?
>
>Done :o) I used the gmail address I had for you since you don't show an email link in your UT account anymore... Let me know if you didn't receive it.

I got it, thanks a million. I don't need this info right now, but it sure comes handy soon.