I have experienced this problem for several times. Whenever I try to setup the new Web project in Visual Studio and then run it in the debug mode, I get error stating that Access is denied to the Temp .Net folder. The solution i had found:
- To give the full permissions to IWAM_COMPUTERNAME account on that folder!
Friday, June 22, 2007
Page breaks for SQL 2005 Reporting
Seems like there is a bug in 2005 SQL Reporting with the InteractiveSize page property setting. Whenever there is an object in the report that have visibility property controlled by the expression (e.g. Hidden set to =Iff(IsNothing(Fields!Result.Value), true, false)), report doesn't break into multiple pages during parsing.
Labels:
bug,
expression,
hidden,
reporting,
SQL 2005,
visibility
Toggled myself crazy on that one
Setting up 'Initial Toggle State' property drove me crazy. If you look at that property - you'll see that by default it is set to 'Collapsed', so the logical thing for the expression would be to use the same kind of terminology, e.g. iff(Fields!Expand.Value = 1, 'Collapsed', 'Expanded').
If only... I spent couple of hours trying to figure out why neither Collapsed nor Expanded were working, i was always getting '+' on the report and it didn't want to change dinamicaly, based on the field value. Turned out that instead of using 'Collapsed' or 'Expanded' - true or false should be used in the expression, as follows -
Expanded = true and Collapsed = false
I ended up just using the report parameter Toggle of type boolean and then setting InitialToggleState to =Parameters!Toggle.Value
So far so good - works fine!
If only... I spent couple of hours trying to figure out why neither Collapsed nor Expanded were working, i was always getting '+' on the report and it didn't want to change dinamicaly, based on the field value. Turned out that instead of using 'Collapsed' or 'Expanded' - true or false should be used in the expression, as follows -
Expanded = true and Collapsed = false
I ended up just using the report parameter Toggle of type boolean and then setting InitialToggleState to =Parameters!Toggle.Value
So far so good - works fine!
SQL 2005 Reporting
It took me a while to figure out - how to use NULL in the Expression Editor. I tried NULL and got the error stating that NULL is not supported anymore, thus System.DBNull should be used.
I tried to use System.DBNull and parser was returning - "DBNull is a type in System and cannot be used as an expression." So much for clearity!
It turned out that 'nothing' should be used instead of null, whenever NULL value needs to be assigned, like in my case:
=IIf(Parameters!FILTER_POA.Value = "NONE", 3, nothing)
I tried to use System.DBNull and parser was returning - "DBNull is a type in System and cannot be used as an expression." So much for clearity!
It turned out that 'nothing' should be used instead of null, whenever NULL value needs to be assigned, like in my case:
=IIf(Parameters!FILTER_POA.Value = "NONE", 3, nothing)
Time to start bloggin
Finaly have decided to start "professional" blog, where i would be posting various findings, tips, tricks, bugs descriptions/walkarounds and anything related to my everyday professional activity.
This way it will be easy for me to reference the things that i have done and/or found.
I will start organazing and posting anything I already have within a couple of days...
Hope this will also be helpfull to public!
This way it will be easy for me to reference the things that i have done and/or found.
I will start organazing and posting anything I already have within a couple of days...
Hope this will also be helpfull to public!
Subscribe to:
Posts (Atom)