Practical Uses for the "Embedded Code" functionality

Dear Anyone,

I understand that there an "Embedded Code" functionality in RS2005. Does anyone know any good uses for this?

Thanks,
Joseph

Normally, you'll use embedded code to create "one off" functions that are (generally) specific to a report -- Maybe something that does a specific calculation that you need which isn't directly supported by VB.NET expressions.

Using embedded code (or code in a custom assembly) gives you greater control over logic flow and alows you to do stuff like more "advanced" conditional statements and looping which you can't do in an expression you place directly behind a control in a report

People will use a custom assembly (which is then referenced by the report) in cases where the functions are reusable, generally more complex. and do things like access system resources (the file system, the network, etc.) .

|||

Is it possible to iterate through a data set in the report in embedded code. If so, how would you reference the data set.

|||No, you can't. It would be nice to be able to just assign a "reporting services dataset" to an "true" ADO.NET datatable and then just walk the table, but there is no such functionality.|||

Hi,

Dont you thik there should be a property for a report that controls how many "records" get displayed on a page?. Currently when I create a report, only 3 records show up and I get 2000 pages. Instead I would prefer 100 records on one page and fewer number of pages?

Or is there any way to do this?

Thanks.