Possible in ActiveReports but not in RS?

What I was talking about is storing the "individual" pages of the
report's intermediate format into a database. Those pages can be
selected, tagged and exported not just to PDF by to any of the other
formats that AR supports. Bryan's response made it appear as if I was
talking about PDF pages which is not the case. Storing the individual
PDF pages is useful in some cases but not as powerful as the scenario
that I mentioned. The scenario I mention can be used to export PDF
pages, html or send faxes in Tiff Formats. MSRS stores the report
intermediate format into a database also, however, the whole report is
stored and cannot be exported as individual pages.
To: James L.: The idea is that you generate a large report once then
retrieve the pages as needed, this can be used where the original data
might have been archived and is no longer available. In case of
statements or old student records and such.
Bryan Keller [MSFT] wrote:
> Reporting Services can easily be used to render single pages of a
report to
> individual PDF files and then those files can be stored in a database
with
> attribution. It is a function of Acrobat and not of the report writer
to
> then merge the PDF files into a single document. With Reporting
Services and
> some custom code, you can meet that scenario hands down. That
functionality
> can probably be accomplished with a number of reporting tools,
Reporting
> Services absolutely being one of the them. Bottom line, Reporting
Services
> can be made to work in that scenario.
>
> --
> Bryan Keller
> Developer Documentation
> SQL Server Reporting Services
>
> A friendly reminder that this posting is provided "AS IS" with no
> warranties, and confers no rights.
>
>
> "Adnan Masood" <adnan.masood@.nextestate.com> wrote in message
> news:urS72IyGEHA.1240@.TK2MSFTNGP10.phx.gbl...
> >
> > Issam Elbaytam, Product Manager Active Reports posted a brief
comparative
> > analysis among Active Reports & MS Reporting Services in his blog
here.
> > http://blogs.pingpoet.com/thoughtchain/archive/2004/04/02/504.aspx
> >
> > Defining the following scenario, he claims this can't be
implemented in
> any
> > other reporting solution.
> >
> > "We have a customer that wanted to print a set of monthly
statements
> (>1000
> > pages) and needed to export these statements (individually) to PDF
based
> > on the users request. He ended up generating the report output
then
> taking
> > the individual pages (using our RDF file format) and inserting each
page
> as
> > a record in a database with some keywords. Now his users can use
his app
> > to pick and choose which of those pages they need. The app would
then
> grab
> > the selected pages from the database, merge them into a new RDF
document
> and
> > export the document to PDF (or any other format) as if it was run
that
> > instant. You simply cannot do that in any other report writer"
> >
> > I'm pretty sure RS has capabilites to implement but would like to
know the
> > opinions of others in the group.
> >
> > Thanks.
> >
> > Adnan Masood
> >
> >Reporting Services already does this but it is not based on pages since
pagination is rendering specific. We do "chunk" our intermediate format as
it is written to the database. We are looking at making this chunking more
granular to improve stream effeciency in future releases.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
<issamelbaytam@.hotmail.com> wrote in message
news:cbaksb$dhf@.odah37.prod.google.com...
> What I was talking about is storing the "individual" pages of the
> report's intermediate format into a database. Those pages can be
> selected, tagged and exported not just to PDF by to any of the other
> formats that AR supports. Bryan's response made it appear as if I was
> talking about PDF pages which is not the case. Storing the individual
> PDF pages is useful in some cases but not as powerful as the scenario
> that I mentioned. The scenario I mention can be used to export PDF
> pages, html or send faxes in Tiff Formats. MSRS stores the report
> intermediate format into a database also, however, the whole report is
> stored and cannot be exported as individual pages.
> To: James L.: The idea is that you generate a large report once then
> retrieve the pages as needed, this can be used where the original data
> might have been archived and is no longer available. In case of
> statements or old student records and such.
>
> Bryan Keller [MSFT] wrote:
>> Reporting Services can easily be used to render single pages of a
> report to
>> individual PDF files and then those files can be stored in a database
> with
>> attribution. It is a function of Acrobat and not of the report writer
> to
>> then merge the PDF files into a single document. With Reporting
> Services and
>> some custom code, you can meet that scenario hands down. That
> functionality
>> can probably be accomplished with a number of reporting tools,
> Reporting
>> Services absolutely being one of the them. Bottom line, Reporting
> Services
>> can be made to work in that scenario.
>> --
>> Bryan Keller
>> Developer Documentation
>> SQL Server Reporting Services
>> A friendly reminder that this posting is provided "AS IS" with no
>> warranties, and confers no rights.
>>
>> "Adnan Masood" <adnan.masood@.nextestate.com> wrote in message
>> news:urS72IyGEHA.1240@.TK2MSFTNGP10.phx.gbl...
>> >
>> > Issam Elbaytam, Product Manager Active Reports posted a brief
> comparative
>> > analysis among Active Reports & MS Reporting Services in his blog
> here.
>> > http://blogs.pingpoet.com/thoughtchain/archive/2004/04/02/504.aspx
>> >
>> > Defining the following scenario, he claims this can't be
> implemented in
>> any
>> > other reporting solution.
>> >
>> > "We have a customer that wanted to print a set of monthly
> statements
>> (>1000
>> > pages) and needed to export these statements (individually) to PDF
> based
>> > on the users request. He ended up generating the report output
> then
>> taking
>> > the individual pages (using our RDF file format) and inserting each
> page
>> as
>> > a record in a database with some keywords. Now his users can use
> his app
>> > to pick and choose which of those pages they need. The app would
> then
>> grab
>> > the selected pages from the database, merge them into a new RDF
> document
>> and
>> > export the document to PDF (or any other format) as if it was run
> that
>> > instant. You simply cannot do that in any other report writer"
>> >
>> > I'm pretty sure RS has capabilites to implement but would like to
> know the
>> > opinions of others in the group.
>> >
>> > Thanks.
>> >
>> > Adnan Masood
>> >
>> >
>

Possible Bug in SQL2005 query?

Hi! This is what happened to me and my colleagues.

We are using SQL 2005. When we were building a view from a table, the
field we selected was not what came out in the output.

Let's say you have 2 specific fields in the table, the second one of
them begins with the letter "L". While your mouse focus is still on the
first field, and you type "L", the focus will jump to the second field.
But now if you left-click it (or press space bar) trying to select it,
in the output panel, you will get the first field.

I hope I get myself understood. Anyone of you happened to experience
the same thing? And what's the explanation for this? The thing is it
didn't happen with SQL 2000. And we are suspecting this to be a bug.chencongwei@.gmail.com wrote:

Quote:

Originally Posted by

Hi! This is what happened to me and my colleagues.
>
We are using SQL 2005. When we were building a view from a table, the
field we selected was not what came out in the output.
>
Let's say you have 2 specific fields in the table, the second one of
them begins with the letter "L". While your mouse focus is still on the
first field, and you type "L", the focus will jump to the second field.
But now if you left-click it (or press space bar) trying to select it,
in the output panel, you will get the first field.
>
I hope I get myself understood. Anyone of you happened to experience
the same thing? And what's the explanation for this? The thing is it
didn't happen with SQL 2000. And we are suspecting this to be a bug.

The place to report a bug is:

http://connect.microsoft.com/SQLServer
My personal recommendation would be that you should avoid the quey/view
designer altogether. Constructing your own views in the editor with the
help of the object browser is a much more powerful and reliable way to
do it.

--
David Portas, SQL Server MVP

Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.

SQL Server Books Online:
http://msdn2.microsoft.com/library/...US,SQL.90).aspx
--