Boundary=“0__=g8AgpNz22zGLRr3EYjM40H603ptKcV13GGzebenycSeH56SsGYxQ0rLw”
–0__=g8AgpNz22zGLRr3EYjM40H603ptKcV13GGzebenycSeH56SsGYxQ0rLw Content-type: text/plain; charset=us-ascii Content-Disposition: inline
Hi Fellow Listers,
Background:
I am using a stored procedure as a data provider (something I do frequently in my reports). More specifically, I EXECUTE this stored procedure through Free-Hand SQL (again, something I
–0__=g8AgpNz22zGLRr3EYjM40H603ptKcV13GGzebenycSeH56SsGYxQ0rLw Content-type: text/plain; charset=iso-8859-1 Content-Disposition: inline
?ve done quite frequently). [ I do it this way so that I can @PROMPT my users for the parameters that I pass to th= e stored
procedure. ]
Additionally, I?m using BO 5.0.1 and Sybase 11.2
The Rub:
Recently, my users came up with a report requirement that the column na= mes
returned by the stored procedure reflect the parameters chosen by the u= sers. In
other words, if the user selects parameters A, B, and E, the stored pro= cedure
returns a block of data with three columns named ?A?, ?B? and ?E?, resp= ectively.
Then, if the user selects parameters B, C, D, the stored procedure retu= rns a
block of data with three columns named ?B?, ?C?, and ?D?, respectively.=
Incidentally, I take care of this column renaming within the Sybase sto= red
procedure.
The above scenario works fine?for one time only. My problem is this:
Upon Refresh of the report (with new parameters chosen) BO responds wit= h the
following dialog box:
?The data provider now contains additional columns of data. You cannot=
simply
add these to the current report as doing so would damage the formats yo= u have
applied.
o Leave the report as is?
o Display the new data in a new report??
I know why this is happening. What I?m wondering is does anyone have a=
creative
workaround to this conundrum? My users inform me that neither of the=
options
presented in the BO dialog box above is acceptable.
Thank you for your time.
Guy Johnson
=
–0__=g8AgpNz22zGLRr3EYjM40H603ptKcV13GGzebenycSeH56SsGYxQ0rLw–
Listserv Archives (BOB member since 2002-06-25)