Jeffrey Williams 3188 (9/3/2012)
Triality (9/3/2012)
Thank you for the direction, however none of these examples are applicable. My clients have access to these reports, so I don't want a parameter driving the data source, as they should not be able to run reports on our other clients....they should only be able to run reports for themselves.The parameter can be data driven - store the allowable data sources in a table and they can only select from those options. How would they get to other clients data anyways?
If you are using a single account for the data source that has access to all client's data - you will need to change that so each client is using their own login.
Another way to avoid this is to publish linked reports to a single source report. In each linked report - you would hardcode the client ID and use a table that has both the clientID and the database. The client ID parameter is hidden and they only see those they have been given access to.
Thanks Jeffrey, this is drilling into my question. I guess I have done a poor job asking it. How can I restrict the parameter options for certain users so that the only option they have is their own? If they selected a different clients name from the parameter, they wouldn't be able to see the report because they wouldn't have permission to their database.
Ideally it wouldn't be a parameter at all, it would just run the report with the correct data source based on which user is logging in. Each client has multiple users with logins, so better yet it would look at a windows usergroup or something similar.