Errors on reports should not occur but when they do it is best to make it clear to the reader that they have just experienced an error.
How evident are the error messages on the 1st report below?
❌ Figure: Bad example - Using the default NoRows property of the table control - error message is not clear enough
✅ Figure: Good example - Use a customized textbox and icon to show the error message in red
Reporting Services allows you to set the 'NoRows' property of a table control to warn your user when there is no data available. This is similar to handle the 'NoData event' in Access report but there is no advanced control on this message, not even a Color property - this has not been improved in RS2005, see our Better Software Suggestions page.
Figure: NoRow property of Table control only allow simple string
Here's how to add a custom "NoData" textbox with a red icon to your report:
Figure: Adding a custom error message to your report
--Expression to set the visibility of the error message controls= iif( Sum(Fields!SaleTotal.Value, "MyDataSet")>0, True, False)
Figure: The Hidden property of the rectangle
--Expression to set the visibility of the main report items= iif( Sum(Fields!SaleTotal.Value, "MyDataSet")>0, **False**, **True**)