Lars Tungen wrote I am seeing the same Oracle error. Looks like all report parameters needs to be in the query string, otherwise you will get an error. In my simple query I didn't use any parameters. When I added "WHERE :ModuleID=:ModuleId AND :PortalID=:PortalID AND :UserID=:UserID AND :TabID=:TabID" it worked. Query giving error: SELECT * FROM T_USERS   Query that works: SELECT * FROM T_USERS WHERE :ModuleID=:ModuleId AND :PortalID=:PortalID AND :UserID=:UserID AND :TabID=:TabID   I guess the Oracle data source hasn't been used that much....

I think I remember seeing this before - are you using the default report module for SQL Server and trying to get it to connect to Oracle? I know I had to re-write some of the oracle implementations of ExecuteHelper, etc to get it to work correctly with the Reports module. I was thinking (silly me) that you were using the oracle version of this for some silly reason..

Sanjay

Sanjay Mehrotra wrote I think I remember seeing this before - are you using the default report module for SQL Server and trying to get it to connect to Oracle? I know I had to re-write some of the oracle implementations of ExecuteHelper, etc to get it to work correctly with the Reports module. I was thinking (silly me) that you were using the oracle version of this for some silly reason.. Sanjay

I am using Report core module with "OracleClient DataProvider" selected as the ADO.NET Data Provider. Maybe the Report module always create all of the 4 parameters on the command object, regardless if they are used in the query string or not. The MS SQL Server ignores the unused parameters. Oracle raises an error.