I have edited several other reports that are similar and those have not had this same problem. I honestly don't think that it would be a stored procedure. But if it was is there anyway that I can find out or locate the procedure to get rid of it. This parameter is really messing with the report and I need to get rid of it completely.
If you look in the database expert, is the datasource listed under tables or under stored procedures? If under stored procedure, this needs to be changed within the SP, and I don't really know anything about that.
You also might check in report options to make sure "read only" is not selected.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.