all groups > sql server reporting services > june 2004 >
sql server reporting services :
Using Sybase stored proc no parameters, cannot load fieldnames
Using the sybase odbc driver to run a stored procedure as the report data set, with no parameters, does not yield the field names. The grid fills with the correct data when clicking on RUN button. Clicking on REFRESH still does not produce field names. When the field names are entered manually via the Dataset Properties dialog, the fieldnames appear but are not usable. That is, whilst the field names are present on the list they are still not useable for the report; they are still not detected. So another REFRESH will then erase the names in the list, back to square one. Do not pass go, do not collect $200 ... DOH! The stored procedure is a simple select statement in which it declares an internal date variable and uses two CASE statements ... hardly rocket science. I would also point out that I've already created numerous reports using parameterised stored procedures off sybase, and also direct sql select statements off sybase.
Are you using the generic query designer (2 panes) or the visual data tools (4 panes). -- Brian Welcker Group Program Manager SQL Server Reporting Services This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "kenobr" <kenobr@discussions.microsoft.com> wrote in message news:4A08AB24-7006-4D41-9320-7DD814322BBE@microsoft.com... > Using the sybase odbc driver to run a stored procedure as the report data > set, with no parameters, does not yield the field names. The grid fills > with the correct data when clicking on RUN button. Clicking on REFRESH > still does not produce field names. When the field names are entered > manually via the Dataset Properties dialog, the fieldnames appear but are > not usable. That is, whilst the field names are present on the list they > are still not useable for the report; they are still not detected. So > another REFRESH will then erase the names in the list, back to square one. > Do not pass go, do not collect $200 ... DOH! > > The stored procedure is a simple select statement in which it declares an > internal date variable and uses two CASE statements ... hardly rocket > science. > > I would also point out that I've already created numerous reports using > parameterised stored procedures off sybase, and also direct sql select > statements off sybase. > > I've been thru the posts, tried those which seemed relevent, to little > avail, so any pointers would be helpful ... Thanks.
I've tried both ... [quoted text, click to view] "Brian Welcker [MSFT]" wrote: > Are you using the generic query designer (2 panes) or the visual data tools > (4 panes). > > -- > Brian Welcker > Group Program Manager > SQL Server Reporting Services > > This posting is provided "AS IS" with no warranties, and confers no rights. > > "kenobr" <kenobr@discussions.microsoft.com> wrote in message > news:4A08AB24-7006-4D41-9320-7DD814322BBE@microsoft.com... > > Using the sybase odbc driver to run a stored procedure as the report data > > set, with no parameters, does not yield the field names. The grid fills > > with the correct data when clicking on RUN button. Clicking on REFRESH > > still does not produce field names. When the field names are entered > > manually via the Dataset Properties dialog, the fieldnames appear but are > > not usable. That is, whilst the field names are present on the list they > > are still not useable for the report; they are still not detected. So > > another REFRESH will then erase the names in the list, back to square one. > > Do not pass go, do not collect $200 ... DOH! > > > > The stored procedure is a simple select statement in which it declares an > > internal date variable and uses two CASE statements ... hardly rocket > > science. > > > > I would also point out that I've already created numerous reports using > > parameterised stored procedures off sybase, and also direct sql select > > statements off sybase. > > > > I've been thru the posts, tried those which seemed relevent, to little > > avail, so any pointers would be helpful ... Thanks. > >
The only workaround I know is to enter the fields manually. -- Brian Welcker Group Program Manager SQL Server Reporting Services This posting is provided "AS IS" with no warranties, and confers no rights. [quoted text, click to view] "kenobr" <kenobr@discussions.microsoft.com> wrote in message news:3228AA8E-6794-4815-8554-FF0CCEEDDD6E@microsoft.com... > I've tried both ... > > "Brian Welcker [MSFT]" wrote: > >> Are you using the generic query designer (2 panes) or the visual data >> tools >> (4 panes). >> >> -- >> Brian Welcker >> Group Program Manager >> SQL Server Reporting Services >> >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> "kenobr" <kenobr@discussions.microsoft.com> wrote in message >> news:4A08AB24-7006-4D41-9320-7DD814322BBE@microsoft.com... >> > Using the sybase odbc driver to run a stored procedure as the report >> > data >> > set, with no parameters, does not yield the field names. The grid fills >> > with the correct data when clicking on RUN button. Clicking on REFRESH >> > still does not produce field names. When the field names are entered >> > manually via the Dataset Properties dialog, the fieldnames appear but >> > are >> > not usable. That is, whilst the field names are present on the list >> > they >> > are still not useable for the report; they are still not detected. So >> > another REFRESH will then erase the names in the list, back to square >> > one. >> > Do not pass go, do not collect $200 ... DOH! >> > >> > The stored procedure is a simple select statement in which it declares >> > an >> > internal date variable and uses two CASE statements ... hardly rocket >> > science. >> > >> > I would also point out that I've already created numerous reports using >> > parameterised stored procedures off sybase, and also direct sql select >> > statements off sybase. >> > >> > I've been thru the posts, tried those which seemed relevent, to little >> > avail, so any pointers would be helpful ... Thanks. >> >> >>
As I said at the outset, this is ok until you hit the Refresh button, when all fields disappear ... how come the grid can populate without a problem, and recognise the field names, but the field list cannot ... this is dumb ... I think it may be an issue with the sybase odbc driver ... thanks anyway. [quoted text, click to view] "Brian Welcker [MSFT]" wrote: > The only workaround I know is to enter the fields manually. > > -- > Brian Welcker > Group Program Manager > SQL Server Reporting Services > > This posting is provided "AS IS" with no warranties, and confers no rights. > > "kenobr" <kenobr@discussions.microsoft.com> wrote in message > news:3228AA8E-6794-4815-8554-FF0CCEEDDD6E@microsoft.com... > > I've tried both ... > > > > "Brian Welcker [MSFT]" wrote: > > > >> Are you using the generic query designer (2 panes) or the visual data > >> tools > >> (4 panes). > >> > >> -- > >> Brian Welcker > >> Group Program Manager > >> SQL Server Reporting Services > >> > >> This posting is provided "AS IS" with no warranties, and confers no > >> rights. > >> > >> "kenobr" <kenobr@discussions.microsoft.com> wrote in message > >> news:4A08AB24-7006-4D41-9320-7DD814322BBE@microsoft.com... > >> > Using the sybase odbc driver to run a stored procedure as the report > >> > data > >> > set, with no parameters, does not yield the field names. The grid fills > >> > with the correct data when clicking on RUN button. Clicking on REFRESH > >> > still does not produce field names. When the field names are entered > >> > manually via the Dataset Properties dialog, the fieldnames appear but > >> > are > >> > not usable. That is, whilst the field names are present on the list > >> > they > >> > are still not useable for the report; they are still not detected. So > >> > another REFRESH will then erase the names in the list, back to square > >> > one. > >> > Do not pass go, do not collect $200 ... DOH! > >> > > >> > The stored procedure is a simple select statement in which it declares > >> > an > >> > internal date variable and uses two CASE statements ... hardly rocket > >> > science. > >> > > >> > I would also point out that I've already created numerous reports using > >> > parameterised stored procedures off sybase, and also direct sql select > >> > statements off sybase. > >> > > >> > I've been thru the posts, tried those which seemed relevent, to little > >> > avail, so any pointers would be helpful ... Thanks. > >> > >> > >> > >
Don't see what you're looking for? Try a search.
|
|
|