|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
MS Reporting, OracleHi,
when I try to run a select-statement to an oracle database (10.1.03) with a parameter from the SQL-area in MS Reporting I get a message like: 'The provider can not determine parameter information and setParameterInfo' is not called' (or similar, the original message is in german). The select statement is like: SELECT LOT, MACHINENUM, ARTICLE10, ARTICLEVARIANT, MEAS_MODE, TOTALCOUNT, PDATE_START, PDATE_END, GRINDCLASS, GRINDLIMIT FROM TBLLOT WHERE (MACHINENUM = @machineNum) ORDER BY LOT There is no problem without the parameter, and there is no problem with the parameter when I use a SQLServer DB. Can someone help? Thanks Ulf @param is SQL Server specific, from BOL
Support for parameters in Oracle depends on the data provider that is used to connect to the Oracle database. If your query contains named parameters (for example, SELECT * FROM <table> WHERE <column name> = :ParameterName) then you must use the Oracle data processing extension. If your query contains unnamed parameters (for example, SELECT * FROM <table> WHERE <column name> = ?), then you must use the OLE DB data processing extension and select Microsoft OLE DB Provider for Oracle as a data provider Show quote "Ulf" <U**@discussions.microsoft.com> wrote in message news:AFA90B76-8342-4EBA-AF07-BA5B01A78715@microsoft.com... > Hi, > when I try to run a select-statement to an oracle database (10.1.03) with > a > parameter from the SQL-area in MS Reporting I get a message like: > 'The provider can not determine parameter information and > setParameterInfo' > is not called' (or similar, the original message is in german). > The select statement is like: > SELECT LOT, MACHINENUM, ARTICLE10, ARTICLEVARIANT, MEAS_MODE, > TOTALCOUNT, PDATE_START, PDATE_END, GRINDCLASS, GRINDLIMIT > FROM TBLLOT > WHERE (MACHINENUM = @machineNum) > ORDER BY LOT > There is no problem without the parameter, and there is no problem with > the > parameter when I use a SQLServer DB. > Can someone help? > Thanks > Ulf Hi Jasper,
thank you for your answer. But this answer does not solve my problem. It is simply not possible to use a syntax like :parameter in MS Reporting, and I have had no success with unnamed parameters. It also seems like a MS Reporting problem (or bug). I expect that MS Reporting will replace my parameter (@machineNum) with the value before sendeing the statement to Oracle but may be I am wrong in this point. I need a method to send a select-statement to Oracle with consideartion of a user input. May be stored procedures will help but I prefer not to use them. ulf Show quote "Jasper Smith" wrote: > @param is SQL Server specific, from BOL > > Support for parameters in Oracle depends on the data provider that is used > to connect to the Oracle database. If your query contains named parameters > (for example, SELECT * FROM <table> WHERE <column name> = :ParameterName) > then you must use the Oracle data processing extension. If your query > contains unnamed parameters (for example, SELECT * FROM <table> WHERE > <column name> = ?), then you must use the OLE DB data processing extension > and select Microsoft OLE DB Provider for Oracle as a data provider > > -- > HTH, > Jasper Smith (SQL Server MVP) > http://www.sqldbatips.com > > > "Ulf" <U**@discussions.microsoft.com> wrote in message > news:AFA90B76-8342-4EBA-AF07-BA5B01A78715@microsoft.com... > > Hi, > > when I try to run a select-statement to an oracle database (10.1.03) with > > a > > parameter from the SQL-area in MS Reporting I get a message like: > > 'The provider can not determine parameter information and > > setParameterInfo' > > is not called' (or similar, the original message is in german). > > The select statement is like: > > SELECT LOT, MACHINENUM, ARTICLE10, ARTICLEVARIANT, MEAS_MODE, > > TOTALCOUNT, PDATE_START, PDATE_END, GRINDCLASS, GRINDLIMIT > > FROM TBLLOT > > WHERE (MACHINENUM = @machineNum) > > ORDER BY LOT > > There is no problem without the parameter, and there is no problem with > > the > > parameter when I use a SQLServer DB. > > Can someone help? > > Thanks > > Ulf > > > Hi Jasper,
thank you for your answer. But this answer does not solve my problem. It is simply not possible to use a syntax like :parameter in MS Reporting, and I have had no success with unnamed parameters. It also seems like a MS Reporting problem (or bug). I expect that MS Reporting will replace my parameter (@machineNum) with the value before sendeing the statement to Oracle but may be I am wrong in this point. I need a method to send a select-statement to Oracle with consideartion of a user input. May be stored procedures will help but I prefer not to use them. ulf Show quote "Ulf" wrote: > Hi, > when I try to run a select-statement to an oracle database (10.1.03) with a > parameter from the SQL-area in MS Reporting I get a message like: > 'The provider can not determine parameter information and setParameterInfo' > is not called' (or similar, the original message is in german). > The select statement is like: > SELECT LOT, MACHINENUM, ARTICLE10, ARTICLEVARIANT, MEAS_MODE, > TOTALCOUNT, PDATE_START, PDATE_END, GRINDCLASS, GRINDLIMIT > FROM TBLLOT > WHERE (MACHINENUM = @machineNum) > ORDER BY LOT > There is no problem without the parameter, and there is no problem with the > parameter when I use a SQLServer DB. > Can someone help? > Thanks > Ulf  |
|||||||||||||||||||||||
Other interesting topics