|
|
You're in the
sql server reporting services
group:Link Reports to System.Data.DataSets?
sql server reporting services:
Today you have to create a data processing extension. In the future
(Widbey/Yukon) there will be a webform control and winform control that would allow this. If you don't want to create a data processing extension then the dataset needs to be generated from RS (either embed the SQL or call a stored procedure). I suggest first looking at using RS without a data processing extension and make sure you understand RS capabilities then if you decide you have to do it with a data processing extension. Remember, RS is a different architecture than Crystal so there will be plenty of places where you need to approach things differently. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Sergio Florez M." <sergioflorezm @ hotmail.com> wrote in message news:OVi4gvm0EHA.4028@TK2MSFTNGP15.phx.gbl... > The mechanism to link a Crystal Report to data is by giving it a > System.Data.DataSet, I was wondering if this same option is possible in > Reporting Services. > > -- > Sergio Florez M. > Miembro activo de www.alianzadev.net > Medellín, Colombia. > El que persevera insiste!!! > >
The mechanism to link a Crystal Report to data is by giving it a
System.Data.DataSet, I was wondering if this same option is possible in Reporting Services. -- Sergio Florez M. Miembro activo de www.alianzadev.net Medellín, Colombia. El que persevera insiste!!!
Well, you can do it, it is just more complex, version 2 this will be much
simplier. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Sergio Florez M." <sergioflorezm @ hotmail.com> wrote in message news:OPn72Nn0EHA.2192@TK2MSFTNGP14.phx.gbl... > uhh... I meant: > > Thank you. The point is that not allowing to generate the reports from a > system.data.DataSet mean that reports can't be rendered from data that only > exists in memory and this is something that Crystal allows and that one of > my customers supposedly needs. > > -- > Sergio Florez M. > Miembro activo de www.alianzadev.net > Medellín, Colombia. > El que persevera insiste!!! > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> wrote in message > news:uFuZgEn0EHA.1404@TK2MSFTNGP11.phx.gbl... > > Today you have to create a data processing extension. In the future > > (Widbey/Yukon) there will be a webform control and winform control that > > would allow this. If you don't want to create a data processing extension > > then the dataset needs to be generated from RS (either embed the SQL or > call > > a stored procedure). I suggest first looking at using RS without a data > > processing extension and make sure you understand RS capabilities then if > > you decide you have to do it with a data processing extension. > > > > Remember, RS is a different architecture than Crystal so there will be > > plenty of places where you need to approach things differently. > > > > -- > > Bruce Loehle-Conger > > MVP SQL Server Reporting Services > > > > > > "Sergio Florez M." <sergioflorezm @ hotmail.com> wrote in message > > news:OVi4gvm0EHA.4028@TK2MSFTNGP15.phx.gbl... > > > The mechanism to link a Crystal Report to data is by giving it a > > > System.Data.DataSet, I was wondering if this same option is possible in > > > Reporting Services. > > > > > > -- > > > Sergio Florez M. > > > Miembro activo de www.alianzadev.net > > > Medellín, Colombia. > > > El que persevera insiste!!! > > > > > > > > > > > >
Thank you. The point is that not allowing to generate the reports from a
system.data.DataSet mean that reports can be rendered from data tha only exists in memory and this is something that Crystal allows and that one of my customers supposedly needs. -- Sergio Florez M. Miembro activo de www.alianzadev.net Medellín, Colombia. El que persevera insiste!!! [quoted text, click to view] "Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> wrote in message news:uFuZgEn0EHA.1404@TK2MSFTNGP11.phx.gbl... > Today you have to create a data processing extension. In the future > (Widbey/Yukon) there will be a webform control and winform control that > would allow this. If you don't want to create a data processing extension > then the dataset needs to be generated from RS (either embed the SQL or call > a stored procedure). I suggest first looking at using RS without a data > processing extension and make sure you understand RS capabilities then if > you decide you have to do it with a data processing extension. > > Remember, RS is a different architecture than Crystal so there will be > plenty of places where you need to approach things differently. > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > > "Sergio Florez M." <sergioflorezm @ hotmail.com> wrote in message > news:OVi4gvm0EHA.4028@TK2MSFTNGP15.phx.gbl... > > The mechanism to link a Crystal Report to data is by giving it a > > System.Data.DataSet, I was wondering if this same option is possible in > > Reporting Services. > > > > -- > > Sergio Florez M. > > Miembro activo de www.alianzadev.net > > Medellín, Colombia. > > El que persevera insiste!!! > > > > > >
uhh... I meant:
Thank you. The point is that not allowing to generate the reports from a system.data.DataSet mean that reports can't be rendered from data that only exists in memory and this is something that Crystal allows and that one of my customers supposedly needs. -- Sergio Florez M. Miembro activo de www.alianzadev.net Medellín, Colombia. El que persevera insiste!!! [quoted text, click to view] "Bruce L-C [MVP]" <bruce_lcNOSPAM@hotmail.com> wrote in message news:uFuZgEn0EHA.1404@TK2MSFTNGP11.phx.gbl... > Today you have to create a data processing extension. In the future > (Widbey/Yukon) there will be a webform control and winform control that > would allow this. If you don't want to create a data processing extension > then the dataset needs to be generated from RS (either embed the SQL or call > a stored procedure). I suggest first looking at using RS without a data > processing extension and make sure you understand RS capabilities then if > you decide you have to do it with a data processing extension. > > Remember, RS is a different architecture than Crystal so there will be > plenty of places where you need to approach things differently. > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > > "Sergio Florez M." <sergioflorezm @ hotmail.com> wrote in message > news:OVi4gvm0EHA.4028@TK2MSFTNGP15.phx.gbl... > > The mechanism to link a Crystal Report to data is by giving it a > > System.Data.DataSet, I was wondering if this same option is possible in > > Reporting Services. > > > > -- > > Sergio Florez M. > > Miembro activo de www.alianzadev.net > > Medellín, Colombia. > > El que persevera insiste!!! > > > > > >
Hi I am not sure that I fully understand your suggestions. I have an ASP.NET application that uses a web form to update an XML dataset. I would like to be able to produce a report from the dataset and ideally I would like to serialize it and pass it as a data source to an RS web service but RS does not seem to support this. I could serialise and persist to SQL Server as a single ntext field that could then be queried to return a complete XML document. Again RS does not seem to handle this. I do not wish to create a full set of SQL Server tables to persist the dataset at the field level just to produce the report (there are rather a lot of items). You indicated that a "data processing extension" might help with this. Could you possibly expand a little more or point me in the right direction? Thanks [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> Today you have to create a data processing extension. In the future > (Widbey/Yukon) there will be a webform control and winform control that > would allow this. If you don't want to create a data processing extension > then the dataset needs to be generated from RS (either embed the SQL or call > a stored procedure). I suggest first looking at using RS without a data > processing extension and make sure you understand RS capabilities then if > you decide you have to do it with a data processing extension. > > Remember, RS is a different architecture than Crystal so there will be > plenty of places where you need to approach things differently. > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > > "Sergio Florez M." <sergioflorezm @ hotmail.com> wrote in message > news:OVi4gvm0EHA.4028@TK2MSFTNGP15.phx.gbl... > > The mechanism to link a Crystal Report to data is by giving it a > > System.Data.DataSet, I was wondering if this same option is possible in > > Reporting Services. > > > > -- > > Sergio Florez M. > > Miembro activo de www.alianzadev.net > > MedellÃn, Colombia. > > El que persevera insiste!!! > > > > > >
I have had some further thoughts and I would be interested to know if the
following approach might work: 1. Create a web-service report that accepts a string parameter and uses a stored procedure as a data source to which it passess the parameter. 2. Write the stored procedure to accept a parameter of type ntext which it passes to sp_xml_preparedocument and then generates the required output using OPENXML(). 3. From the asp.net application, serialise the xml from the dataset as a string and pass as a parameter to the web-service report. Thanks [quoted text, click to view] "njr" wrote:
> > Hi > I am not sure that I fully understand your suggestions. I have an ASP.NET > application that uses a web form to update an XML dataset. I would like to be > able to produce a report from the dataset and ideally I would like to > serialize it and pass it as a data source to an RS web service but RS does > not seem to support this. I could serialise and persist to SQL Server as a > single ntext field that could then be queried to return a complete XML > document. Again RS does not seem to handle this. I do not wish to create a > full set of SQL Server tables to persist the dataset at the field level just > to produce the report (there are rather a lot of items). > > You indicated that a "data processing extension" might help with this. Could > you possibly expand a little more or point me in the right direction? > > Thanks > > "Bruce L-C [MVP]" wrote: > > > Today you have to create a data processing extension. In the future > > (Widbey/Yukon) there will be a webform control and winform control that > > would allow this. If you don't want to create a data processing extension > > then the dataset needs to be generated from RS (either embed the SQL or call > > a stored procedure). I suggest first looking at using RS without a data > > processing extension and make sure you understand RS capabilities then if > > you decide you have to do it with a data processing extension. > > > > Remember, RS is a different architecture than Crystal so there will be > > plenty of places where you need to approach things differently. > > > > -- > > Bruce Loehle-Conger > > MVP SQL Server Reporting Services > > > > > > "Sergio Florez M." <sergioflorezm @ hotmail.com> wrote in message > > news:OVi4gvm0EHA.4028@TK2MSFTNGP15.phx.gbl... > > > The mechanism to link a Crystal Report to data is by giving it a > > > System.Data.DataSet, I was wondering if this same option is possible in > > > Reporting Services. > > > > > > -- > > > Sergio Florez M. > > > Miembro activo de www.alianzadev.net > > > MedellÃn, Colombia. > > > El que persevera insiste!!! > > > > > > > > > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |