Passing a parameter onto a Oracle database

I am connected to an oracle database and wish to allow the users enter a
ProdID, normally in SQL the criteria in the dataset would be =@.ProdID and
this would be passed onto the report. In oracle it sees this as a text and
encloses parameter in quotes '=@.ProdID'
Is it possible to use this expression in reporting services when attached to
an oracle database or is this something that cannot be fixedThe managed Oracle data provider uses a ':' to mark named parameters
(instead of '@.'); the OleDB provider for Oracle only allows unnamed
parameters (using '?'). The following KB article explains more details:
http://support.microsoft.com/default.aspx?scid=kb;en-us;834305
Examples:
Managed Oracle provider (named parameters):
select * from table where ename = :parameter
OleDB for Oracle (unnamed parameters):
select * from table where ename = ?
Note: the Visual Data Tools (VDT) query designer (4 panes) actually uses OLE
DB in the preview pane. The text-based generic query designer (GQD; 2 panes)
uses the .NET provider for Oracle. Generally, you will achieve better
results when using GQD with Oracle.
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kevin" <Kevin@.discussions.microsoft.com> wrote in message
news:717C796D-3694-4B5C-92C2-8E701CF8C428@.microsoft.com...
>I am connected to an oracle database and wish to allow the users enter a
> ProdID, normally in SQL the criteria in the dataset would be =@.ProdID and
> this would be passed onto the report. In oracle it sees this as a text
> and
> encloses parameter in quotes '=@.ProdID'
> Is it possible to use this expression in reporting services when attached
> to
> an oracle database or is this something that cannot be fixed|||Thanks Robert, now I know what I must do.
"Robert Bruckner [MSFT]" wrote:
> The managed Oracle data provider uses a ':' to mark named parameters
> (instead of '@.'); the OleDB provider for Oracle only allows unnamed
> parameters (using '?'). The following KB article explains more details:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;834305
> Examples:
> Managed Oracle provider (named parameters):
> select * from table where ename = :parameter
> OleDB for Oracle (unnamed parameters):
> select * from table where ename = ?
> Note: the Visual Data Tools (VDT) query designer (4 panes) actually uses OLE
> DB in the preview pane. The text-based generic query designer (GQD; 2 panes)
> uses the .NET provider for Oracle. Generally, you will achieve better
> results when using GQD with Oracle.
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Kevin" <Kevin@.discussions.microsoft.com> wrote in message
> news:717C796D-3694-4B5C-92C2-8E701CF8C428@.microsoft.com...
> >I am connected to an oracle database and wish to allow the users enter a
> > ProdID, normally in SQL the criteria in the dataset would be =@.ProdID and
> > this would be passed onto the report. In oracle it sees this as a text
> > and
> > encloses parameter in quotes '=@.ProdID'
> >
> > Is it possible to use this expression in reporting services when attached
> > to
> > an oracle database or is this something that cannot be fixed
>
>