BUG: provider cannot derive parameter information and setparameter

I create reports on an oracle db. I use the correct oracle provider. When i
create a report parameter and run it in the datatab, it says "provider cannot
derive parameter information and setparameterinfo has not been called".
However if I go to generic query designer or the layout tab, the report
parameter works correctly.
This appears to be a bug!!. Could someone from Microsoft please confirm this.
Much appreciated
Kevin WeirYou will need an Oracle Client 8.1.7 or later installed on the server and
the client machines. Please verify you are not using an older Oracle client.
Regardless of the data provider (OleDB or managed), they will need the
Oracle Client (OCI) to actually talk to the Oracle server.
As indicated in several other discussion threads on this newsgroup, the
visual query designer (with 4 panes) is a shared component of the VS
framework (which is unable to use the managed provider and uses the MS OleDB
provider for Oracle instead). Even if you select "Oracle" from the data
source dialog, the visual query designer will actually use the OleDB
provider, while the generic query designer will *always* use the data
provider you actually selected. I.e. "Oracle" is the managed provider of the
.NET framework. Most likely you are using named parameters (e.g. :par1)
which are only supported by the managed Oracle provider (hence the query
execution works successfully in the generic text-based query designer). The
OleDB provider only supports unnamed parameters.
Some information can also be found in this KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;834305
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kevin Weir" <KevinWeir@.discussions.microsoft.com> wrote in message
news:D359816A-16DD-4CDD-959D-C5B066474C15@.microsoft.com...
> I create reports on an oracle db. I use the correct oracle provider. When
i
> create a report parameter and run it in the datatab, it says "provider
cannot
> derive parameter information and setparameterinfo has not been called".
> However if I go to generic query designer or the layout tab, the report
> parameter works correctly.
> This appears to be a bug!!. Could someone from Microsoft please confirm
this.
> Much appreciated
> Kevin Weir
>|||Just adding another comment: The graphical query designer in RS is the VDT
component which supports only a limited list of data providers as outlined
in this KB article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;811241
The text-based generic query designer in RS supports almost any data
provider.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Robert Bruckner [MSFT]" <robruc@.online.microsoft.com> wrote in message
news:%23AOfSgAsEHA.3396@.tk2msftngp13.phx.gbl...
> You will need an Oracle Client 8.1.7 or later installed on the server and
> the client machines. Please verify you are not using an older Oracle
client.
> Regardless of the data provider (OleDB or managed), they will need the
> Oracle Client (OCI) to actually talk to the Oracle server.
> As indicated in several other discussion threads on this newsgroup, the
> visual query designer (with 4 panes) is a shared component of the VS
> framework (which is unable to use the managed provider and uses the MS
OleDB
> provider for Oracle instead). Even if you select "Oracle" from the data
> source dialog, the visual query designer will actually use the OleDB
> provider, while the generic query designer will *always* use the data
> provider you actually selected. I.e. "Oracle" is the managed provider of
the
> .NET framework. Most likely you are using named parameters (e.g. :par1)
> which are only supported by the managed Oracle provider (hence the query
> execution works successfully in the generic text-based query designer).
The
> OleDB provider only supports unnamed parameters.
> Some information can also be found in this KB article:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;834305
> --
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Kevin Weir" <KevinWeir@.discussions.microsoft.com> wrote in message
> news:D359816A-16DD-4CDD-959D-C5B066474C15@.microsoft.com...
> > I create reports on an oracle db. I use the correct oracle provider.
When
> i
> > create a report parameter and run it in the datatab, it says "provider
> cannot
> > derive parameter information and setparameterinfo has not been called".
> >
> > However if I go to generic query designer or the layout tab, the report
> > parameter works correctly.
> >
> > This appears to be a bug!!. Could someone from Microsoft please confirm
> this.
> >
> > Much appreciated
> > Kevin Weir
> >
>|||Hi Robert
Thanks for your response. Your comments have clarrified this issue for me.
I did not realize the OLE DB provider was being used by Visual Designer
which accounts for different behavior in Generic Query designer.
For others that may read this thread we are using Oracle 9.2.0.4 client with
named parameters. For example, one of our queries might look like this:
SELECT * FROM EMPLOYEES WHERE EMPLOYEE_ID = :EMPLOYEE_ID
Regards
Kevin
"Robert Bruckner [MSFT]" wrote:
> You will need an Oracle Client 8.1.7 or later installed on the server and
> the client machines. Please verify you are not using an older Oracle client.
> Regardless of the data provider (OleDB or managed), they will need the
> Oracle Client (OCI) to actually talk to the Oracle server.
> As indicated in several other discussion threads on this newsgroup, the
> visual query designer (with 4 panes) is a shared component of the VS
> framework (which is unable to use the managed provider and uses the MS OleDB
> provider for Oracle instead). Even if you select "Oracle" from the data
> source dialog, the visual query designer will actually use the OleDB
> provider, while the generic query designer will *always* use the data
> provider you actually selected. I.e. "Oracle" is the managed provider of the
> ..NET framework. Most likely you are using named parameters (e.g. :par1)
> which are only supported by the managed Oracle provider (hence the query
> execution works successfully in the generic text-based query designer). The
> OleDB provider only supports unnamed parameters.
> Some information can also be found in this KB article:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;834305
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Kevin Weir" <KevinWeir@.discussions.microsoft.com> wrote in message
> news:D359816A-16DD-4CDD-959D-C5B066474C15@.microsoft.com...
> > I create reports on an oracle db. I use the correct oracle provider. When
> i
> > create a report parameter and run it in the datatab, it says "provider
> cannot
> > derive parameter information and setparameterinfo has not been called".
> >
> > However if I go to generic query designer or the layout tab, the report
> > parameter works correctly.
> >
> > This appears to be a bug!!. Could someone from Microsoft please confirm
> this.
> >
> > Much appreciated
> > Kevin Weir
> >
>
>