I’ve been playing with Microsoft Report Builder 1.0 recently as we were asked to create an ad-hoc reporting model for some of our users to create their own reports.
When adding filters to reports the application has always provided drop-down lists of available values for each condition I select, however, this only seems to be the case when running the Report Builder on my own PC building reports over a database on my local SQL Server.
When I try accessing a remote database from my Report Builder, or when I access my own database from someone else’s PC, the drop-down lists are not generated, meaning the user has to manually enter text values into the parameter fields.
Has anyone else had this problem or found a way around it? Is this behaviour intentional, maybe for performance or security reasons? It seems a bit odd that this would be the case, but stranger things have happened!
I’ve run into this problem, there were 2 reasons I saw it happening.
The datasource to the report model was not set to use Windows Integrated Security. I have found that if it’s set to anything else the drop-downs don’t work.
There were database permission issues on the tables/views that the Models were using. I ended up reworking the models to use views that our end users had permissions to, instead of using the restricted tables.
I have found Report Builder 1.0 and 2005 Models to be fickle and difficult to use and maintain and very limited in functionality.