print button exists without SP2

In the preeview mode of the report designer the print button and the
print-preeview button are available, activated and can be used.
But this buttons are not displayed if the report is displayed in the IE.
Now I read, that printing will be possible with SP2. Printing is a feature
and not a bug and SPs are supposedly not "Feature Packs".
Printing is a key feature in our project and was suggested. And for the
reason it was to use in the report designer we assumed it works. Now we are
in the testing after a several week development and where is printing?
I realy wish to change my job for a time with the MVPs and MS staff, who are
joking about this subject in this news group. This is nothing to joke about
if you get payed for results and if you are realy responsible for what are
you doing as an self employed developer.
Again I'm realy shoked about the real ripeness of reporting services and the
dimension in which Microsoft is lying by the promotion of there products.Are you asking for help or just being insulting? If you want help I'll try
to help you but instead you just insult MVPs and MS. I have never laughed at
anyone's problem and I help lots of people. And guess what, I don't get paid
to help anyone. I don't see you helping anyone.
That said, I'll help you anyway, although I don't know why I bother. First
off. If you have a print preview button you are using a beta of SP2. That is
fine but a beta means a beta (pre-release) and it sounds to me like you
should not being using a beta product. That said, I can guess what is
happening. SP2 will have two places to install, the development environment
and on the server. It sounds to me like you applied it in the development
environment (hence you see the print button) but did not apply it on the
server.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Dev Main" <DevMain@.discussions.microsoft.com> wrote in message
news:3CC0DB60-8321-4F86-862D-8E356111EAD0@.microsoft.com...
> In the preeview mode of the report designer the print button and the
> print-preeview button are available, activated and can be used.
> But this buttons are not displayed if the report is displayed in the IE.
> Now I read, that printing will be possible with SP2. Printing is a feature
> and not a bug and SPs are supposedly not "Feature Packs".
> Printing is a key feature in our project and was suggested. And for the
> reason it was to use in the report designer we assumed it works. Now we
are
> in the testing after a several week development and where is printing?
> I realy wish to change my job for a time with the MVPs and MS staff, who
are
> joking about this subject in this news group. This is nothing to joke
about
> if you get payed for results and if you are realy responsible for what are
> you doing as an self employed developer.
> Again I'm realy shoked about the real ripeness of reporting services and
the
> dimension in which Microsoft is lying by the promotion of there products.|||Dev Main wrote:
> Again I'm realy shoked about the real ripeness of reporting services
> and the dimension in which Microsoft is lying by the promotion of
> there products.
Devmaaan,
i waste my time with reading you confuse posts.
Please!...let it be and develop your reports with an other software.
Did you pay for reporting services? I assume that you dont licensed a
sql-server-license only for reporting...hmm?
regards
frank|||Is this really the place to whine about Microsoft putting features into
Service Packs? I thought this was a place for answers not a place to
discuss your plight as a self employed developer. I have only witnessed
helpfulness from the Microsoft guys. We not me personally as I try to
help answer questions rather than ask them. I try to contribute not
just tear down and whine about what is in or not in Reporting Services.
I have 2 things to point out. 1) Reporting Services is basically
free...although there are some qualifications to that statement. 2)
Reporting Services is in version 1 still.
You aren't much of a developer if you don't have a little bit of
respect for a version 1 product. Maybe DevMain, you need to be less
critical and more helpful. We all have our issues...but we are working
together to resolve them. That is what this group is for...not for your
destructive criticism of people who are just trying to help.
And just as I though (as I look at your other postings) you are the
same guy that is "Shoked" about something else. Dude...buy
Crystal...see if they care...and let the Reporting Services bus roll
on without you. You get too "shoked" all of the time...and by the
way...I believe it's Shocked...not shoked...I have no idea what shoked
is.
And last...incase you are wondering...I am not employed by Microsoft. I
am just a guy trying to get answers to a product that I really like.|||SP2 is coming out shortly and the long awaited client side printing
functionality will be there.
You should really familiarize yourself with the features list of a release
before architecting and developing a solution. It'll help you avoid
surprises.
Also, you may not want to lash out at the very people who can probably
answers your technical questions.
--
Adrian M.
MCP
"Dev Main" <DevMain@.discussions.microsoft.com> wrote in message
news:3CC0DB60-8321-4F86-862D-8E356111EAD0@.microsoft.com...
> In the preeview mode of the report designer the print button and the
> print-preeview button are available, activated and can be used.
> But this buttons are not displayed if the report is displayed in the IE.
> Now I read, that printing will be possible with SP2. Printing is a feature
> and not a bug and SPs are supposedly not "Feature Packs".
> Printing is a key feature in our project and was suggested. And for the
> reason it was to use in the report designer we assumed it works. Now we
> are
> in the testing after a several week development and where is printing?
> I realy wish to change my job for a time with the MVPs and MS staff, who
> are
> joking about this subject in this news group. This is nothing to joke
> about
> if you get payed for results and if you are realy responsible for what are
> you doing as an self employed developer.
> Again I'm realy shoked about the real ripeness of reporting services and
> the
> dimension in which Microsoft is lying by the promotion of there products.|||It is not true that I don't help others! There are articles I wrote answeres.
But I like to become a bit more expert in the subject before teaching others
how to do something.
"You love the product and I have no respect for a version 1.0".
I'm responsible in real live projects for predictable results in a
predictable time. And from the facts I will describe belowe Reporting
Services is a promissing beta version with potential for a great product.
Promise: Reports can be exported to excel and the data can be processed there.
Reality: With "can grow" option on fields the layout in excel is unusable.
Sort function doesn't work on export to excel (not to csv). (Excel XP!). On
CSV Export the fields become seperated with a "," what is not supported by
Excel and not supported by Access and is stupid too, becouse whats about ","
in the field values?
Promise: Group report data like in MS Access
Reality: With the list control ("the one for Access users"). Nested list
controls makes the report frequently corrupt. If the fields are located
without distance between it, the fields displayed somewhere in the page. If I
place them with a distance between them the formating in excel is unusefull.
Promise: Reporting Services provides Parameters
Realitiy:
- The parameter captions can not be localizesed.
- The dropdown lists can not be localizesed.
- With cascading parameters the dropdownlists are requeried, even if thy are
not depend on a selected field.
- The dropdownlist are requeried when the report get rendered.
- If several parameters depend all on the same other parameter each
selection in one of the drop down list couse all drop downlists beeing
requeried. With 6 parameters I've got the drop down lists 26 times requeried,
but only 5 times are necessary.
- Multiple selection are relized by enter the values manualy by the user
(Tip from MVPs)
Promise: Localization
Reality: Localization is not possible! What ever you say it is not in real
live projects. You can't localize report names and descriptions in the report
manager. You can't localize Parameter captions or drop down lists. You can't
implement a language selection for the user. And much more. The solution is
to build your own report manager in a asp application and provide for the
parameter input separat forms.
Promise: Printing reports. From the promotion everybody I'm talking about
expected to print out a report. I think I read this feature, but in this
moment I don't find it again. Two members of our project team said they read
it too.
Promisse: Custom assembly
Realitity: I replaced it with a update, but reporting services still used
the previous version. How comes this, if I replaced physicaly the file? Ahhh
there is a copy of the file somewhere in "...\.net Framework\...\temp"
directory. "Oh chef, I don't achived the result I promised! But I found
something out tonight what makes me love the Microsoft product much more then
my family. Could I get a salary increase?"
I could enumerate much more issues.
That the product is for free is no argument. In our case we purchased a SQL
Server license only to use reporting services. The data are hosted in a
oracle database. And independend from if it costs something or not, it is not
my fault that it is for free and if it would be not for free we have
purchased it.
About the printing function I found in the middle of my dispair a post from
a MVP posted in October where he wrote that the user should pray to good and
this brings the service pack 2 possibly to chrismas.
Reality:
"Dev Main" wrote:
> In the preeview mode of the report designer the print button and the
> print-preeview button are available, activated and can be used.
> But this buttons are not displayed if the report is displayed in the IE.
> Now I read, that printing will be possible with SP2. Printing is a feature
> and not a bug and SPs are supposedly not "Feature Packs".
> Printing is a key feature in our project and was suggested. And for the
> reason it was to use in the report designer we assumed it works. Now we are
> in the testing after a several week development and where is printing?
> I realy wish to change my job for a time with the MVPs and MS staff, who are
> joking about this subject in this news group. This is nothing to joke about
> if you get payed for results and if you are realy responsible for what are
> you doing as an self employed developer.
> Again I'm realy shoked about the real ripeness of reporting services and the
> dimension in which Microsoft is lying by the promotion of there products.|||Send a description of the problems/issues you have noticed to:
mswish@.microsoft.com
http://www.microsoft.com/mswish
Adrian M.
MCP
"Dev Main" <DevMain@.discussions.microsoft.com> wrote in message
news:DAE6F1C5-7614-46AB-97F5-B9287B8D192B@.microsoft.com...
> It is not true that I don't help others! There are articles I wrote
> answeres.
> But I like to become a bit more expert in the subject before teaching
> others
> how to do something.
> "You love the product and I have no respect for a version 1.0".
> I'm responsible in real live projects for predictable results in a
> predictable time. And from the facts I will describe belowe Reporting
> Services is a promissing beta version with potential for a great product.
> Promise: Reports can be exported to excel and the data can be processed
> there.
> Reality: With "can grow" option on fields the layout in excel is unusable.
> Sort function doesn't work on export to excel (not to csv). (Excel XP!).
> On
> CSV Export the fields become seperated with a "," what is not supported by
> Excel and not supported by Access and is stupid too, becouse whats about
> ","
> in the field values?
> Promise: Group report data like in MS Access
> Reality: With the list control ("the one for Access users"). Nested list
> controls makes the report frequently corrupt. If the fields are located
> without distance between it, the fields displayed somewhere in the page.
> If I
> place them with a distance between them the formating in excel is
> unusefull.
> Promise: Reporting Services provides Parameters
> Realitiy:
> - The parameter captions can not be localizesed.
> - The dropdown lists can not be localizesed.
> - With cascading parameters the dropdownlists are requeried, even if thy
> are
> not depend on a selected field.
> - The dropdownlist are requeried when the report get rendered.
> - If several parameters depend all on the same other parameter each
> selection in one of the drop down list couse all drop downlists beeing
> requeried. With 6 parameters I've got the drop down lists 26 times
> requeried,
> but only 5 times are necessary.
> - Multiple selection are relized by enter the values manualy by the user
> (Tip from MVPs)
> Promise: Localization
> Reality: Localization is not possible! What ever you say it is not in real
> live projects. You can't localize report names and descriptions in the
> report
> manager. You can't localize Parameter captions or drop down lists. You
> can't
> implement a language selection for the user. And much more. The solution
> is
> to build your own report manager in a asp application and provide for the
> parameter input separat forms.
> Promise: Printing reports. From the promotion everybody I'm talking about
> expected to print out a report. I think I read this feature, but in this
> moment I don't find it again. Two members of our project team said they
> read
> it too.
> Promisse: Custom assembly
> Realitity: I replaced it with a update, but reporting services still used
> the previous version. How comes this, if I replaced physicaly the file?
> Ahhh
> there is a copy of the file somewhere in "...\.net Framework\...\temp"
> directory. "Oh chef, I don't achived the result I promised! But I found
> something out tonight what makes me love the Microsoft product much more
> then
> my family. Could I get a salary increase?"
> I could enumerate much more issues.
> That the product is for free is no argument. In our case we purchased a
> SQL
> Server license only to use reporting services. The data are hosted in a
> oracle database. And independend from if it costs something or not, it is
> not
> my fault that it is for free and if it would be not for free we have
> purchased it.
> About the printing function I found in the middle of my dispair a post
> from
> a MVP posted in October where he wrote that the user should pray to good
> and
> this brings the service pack 2 possibly to chrismas.
>
>
>
> Reality:
> "Dev Main" wrote:
>> In the preeview mode of the report designer the print button and the
>> print-preeview button are available, activated and can be used.
>> But this buttons are not displayed if the report is displayed in the IE.
>> Now I read, that printing will be possible with SP2. Printing is a
>> feature
>> and not a bug and SPs are supposedly not "Feature Packs".
>> Printing is a key feature in our project and was suggested. And for the
>> reason it was to use in the report designer we assumed it works. Now we
>> are
>> in the testing after a several week development and where is printing?
>> I realy wish to change my job for a time with the MVPs and MS staff, who
>> are
>> joking about this subject in this news group. This is nothing to joke
>> about
>> if you get payed for results and if you are realy responsible for what
>> are
>> you doing as an self employed developer.
>> Again I'm realy shoked about the real ripeness of reporting services and
>> the
>> dimension in which Microsoft is lying by the promotion of there products.|||If you have a question, next time post the question and people will try to
help. You were very insulting last time.
Let me be very very clear here because you missed the point again. Printing
from the client will be released with SP2 (Service Pack 2). This will be
released this month.
Point number 2. It is a release 1 product. Certain things are hard to do (I
am currently working around an Excel issue) so yes, there are issues. So far
I have seen that most issues have a work around (most but not all).
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Dev Main" <DevMain@.discussions.microsoft.com> wrote in message
news:DAE6F1C5-7614-46AB-97F5-B9287B8D192B@.microsoft.com...
> It is not true that I don't help others! There are articles I wrote
answeres.
> But I like to become a bit more expert in the subject before teaching
others
> how to do something.
> "You love the product and I have no respect for a version 1.0".
> I'm responsible in real live projects for predictable results in a
> predictable time. And from the facts I will describe belowe Reporting
> Services is a promissing beta version with potential for a great product.
> Promise: Reports can be exported to excel and the data can be processed
there.
> Reality: With "can grow" option on fields the layout in excel is unusable.
> Sort function doesn't work on export to excel (not to csv). (Excel XP!).
On
> CSV Export the fields become seperated with a "," what is not supported by
> Excel and not supported by Access and is stupid too, becouse whats about
","
> in the field values?
> Promise: Group report data like in MS Access
> Reality: With the list control ("the one for Access users"). Nested list
> controls makes the report frequently corrupt. If the fields are located
> without distance between it, the fields displayed somewhere in the page.
If I
> place them with a distance between them the formating in excel is
unusefull.
> Promise: Reporting Services provides Parameters
> Realitiy:
> - The parameter captions can not be localizesed.
> - The dropdown lists can not be localizesed.
> - With cascading parameters the dropdownlists are requeried, even if thy
are
> not depend on a selected field.
> - The dropdownlist are requeried when the report get rendered.
> - If several parameters depend all on the same other parameter each
> selection in one of the drop down list couse all drop downlists beeing
> requeried. With 6 parameters I've got the drop down lists 26 times
requeried,
> but only 5 times are necessary.
> - Multiple selection are relized by enter the values manualy by the user
> (Tip from MVPs)
> Promise: Localization
> Reality: Localization is not possible! What ever you say it is not in real
> live projects. You can't localize report names and descriptions in the
report
> manager. You can't localize Parameter captions or drop down lists. You
can't
> implement a language selection for the user. And much more. The solution
is
> to build your own report manager in a asp application and provide for the
> parameter input separat forms.
> Promise: Printing reports. From the promotion everybody I'm talking about
> expected to print out a report. I think I read this feature, but in this
> moment I don't find it again. Two members of our project team said they
read
> it too.
> Promisse: Custom assembly
> Realitity: I replaced it with a update, but reporting services still used
> the previous version. How comes this, if I replaced physicaly the file?
Ahhh
> there is a copy of the file somewhere in "...\.net Framework\...\temp"
> directory. "Oh chef, I don't achived the result I promised! But I found
> something out tonight what makes me love the Microsoft product much more
then
> my family. Could I get a salary increase?"
> I could enumerate much more issues.
> That the product is for free is no argument. In our case we purchased a
SQL
> Server license only to use reporting services. The data are hosted in a
> oracle database. And independend from if it costs something or not, it is
not
> my fault that it is for free and if it would be not for free we have
> purchased it.
> About the printing function I found in the middle of my dispair a post
from
> a MVP posted in October where he wrote that the user should pray to good
and
> this brings the service pack 2 possibly to chrismas.
>
>
>
> Reality:
> "Dev Main" wrote:
> > In the preeview mode of the report designer the print button and the
> > print-preeview button are available, activated and can be used.
> >
> > But this buttons are not displayed if the report is displayed in the IE.
> >
> > Now I read, that printing will be possible with SP2. Printing is a
feature
> > and not a bug and SPs are supposedly not "Feature Packs".
> >
> > Printing is a key feature in our project and was suggested. And for the
> > reason it was to use in the report designer we assumed it works. Now we
are
> > in the testing after a several week development and where is printing?
> >
> > I realy wish to change my job for a time with the MVPs and MS staff, who
are
> > joking about this subject in this news group. This is nothing to joke
about
> > if you get payed for results and if you are realy responsible for what
are
> > you doing as an self employed developer.
> >
> > Again I'm realy shoked about the real ripeness of reporting services and
the
> > dimension in which Microsoft is lying by the promotion of there
products.|||Dev Main, you need to chill out man.
RS was released early because of user pressure. MS weren't planning to
release it until SQL2005. Considering that, it's a suprisingly good
release.
Yes it is limited in some areas, like printing, but exporting to PDF is
a satisfactory compromise for most.
RS is designed as a web based tool so printing is not it's main reason
for existence.
If you want to control reporting centrally and deploy to intranet, it's
the best tool for the job. It does require database knowledge and VB
knowledge helps too. MS make no secret of that.
You CAN localise, it might require some effort but it can be done.
As for Access Reporting, you just can't compare RS with Access
reporting, they are aimed at completely different audiences.
Excel export works OK for most cases, but there are issues.
The comma in a field issue with CSV is a perrenial CSV problem, but
surround text with delimiters, e.g. Quotes " and it's OK. This isn't an
RS issue.
I have my suspicions that as an Oracle devotee you are fairly anti-MS.
I don't have a problem with that, but I do feel you're being a little
unfair to the RS team with your rant. For once, Microsofts claim to be
'innovative' is bourne out by this product, give them a break.
Like any application, you need to evaluate it. It's not suitable for
all situations or organisations but don't have a go at them if that's
the case, work with them, they will help.
FYI: The print feature is coming imminently with SP2.
Regards
Chris
Dev Main wrote:
> It is not true that I don't help others! There are articles I wrote
> answeres. But I like to become a bit more expert in the subject
> before teaching others how to do something.
> "You love the product and I have no respect for a version 1.0".
> I'm responsible in real live projects for predictable results in a
> predictable time. And from the facts I will describe belowe Reporting
> Services is a promissing beta version with potential for a great
> product.
> Promise: Reports can be exported to excel and the data can be
> processed there. Reality: With "can grow" option on fields the
> layout in excel is unusable. Sort function doesn't work on export to
> excel (not to csv). (Excel XP!). On CSV Export the fields become
> seperated with a "," what is not supported by Excel and not supported
> by Access and is stupid too, becouse whats about "," in the field
> values?
> Promise: Group report data like in MS Access
> Reality: With the list control ("the one for Access users"). Nested
> list controls makes the report frequently corrupt. If the fields are
> located without distance between it, the fields displayed somewhere
> in the page. If I place them with a distance between them the
> formating in excel is unusefull.
> Promise: Reporting Services provides Parameters
> Realitiy:
> - The parameter captions can not be localizesed.
> - The dropdown lists can not be localizesed.
> - With cascading parameters the dropdownlists are requeried, even if
> thy are not depend on a selected field.
> - The dropdownlist are requeried when the report get rendered.
> - If several parameters depend all on the same other parameter each
> selection in one of the drop down list couse all drop downlists
> beeing requeried. With 6 parameters I've got the drop down lists 26
> times requeried, but only 5 times are necessary.
> - Multiple selection are relized by enter the values manualy by the
> user (Tip from MVPs)
> Promise: Localization
> Reality: Localization is not possible! What ever you say it is not in
> real live projects. You can't localize report names and descriptions
> in the report manager. You can't localize Parameter captions or drop
> down lists. You can't implement a language selection for the user.
> And much more. The solution is to build your own report manager in a
> asp application and provide for the parameter input separat forms.
> Promise: Printing reports. From the promotion everybody I'm talking
> about expected to print out a report. I think I read this feature,
> but in this moment I don't find it again. Two members of our project
> team said they read it too.
> Promisse: Custom assembly
> Realitity: I replaced it with a update, but reporting services still
> used the previous version. How comes this, if I replaced physicaly
> the file? Ahhh there is a copy of the file somewhere in "...\.net
> Framework\...\temp" directory. "Oh chef, I don't achived the result I
> promised! But I found something out tonight what makes me love the
> Microsoft product much more then my family. Could I get a salary
> increase?"
> I could enumerate much more issues.
> That the product is for free is no argument. In our case we purchased
> a SQL Server license only to use reporting services. The data are
> hosted in a oracle database. And independend from if it costs
> something or not, it is not my fault that it is for free and if it
> would be not for free we have purchased it.
> About the printing function I found in the middle of my dispair a
> post from a MVP posted in October where he wrote that the user should
> pray to good and this brings the service pack 2 possibly to chrismas.
>
>
>
> Reality:
> "Dev Main" wrote:
> > In the preeview mode of the report designer the print button and
> > the print-preeview button are available, activated and can be used.
> >
> > But this buttons are not displayed if the report is displayed in
> > the IE.
> >
> > Now I read, that printing will be possible with SP2. Printing is a
> > feature and not a bug and SPs are supposedly not "Feature Packs".
> >
> > Printing is a key feature in our project and was suggested. And for
> > the reason it was to use in the report designer we assumed it
> > works. Now we are in the testing after a several week development
> > and where is printing?
> >
> > I realy wish to change my job for a time with the MVPs and MS
> > staff, who are joking about this subject in this news group. This
> > is nothing to joke about if you get payed for results and if you
> > are realy responsible for what are you doing as an self employed
> > developer.
> >
> > Again I'm realy shoked about the real ripeness of reporting
> > services and the dimension in which Microsoft is lying by the
> > promotion of there products.|||I would gather by the difficulty that I have reading your posts that
the issues you are having with your reports are users/developer
issues...not so much the product.
I would fire whoever it was in your organization that evaluated SRS and
had you guys buy SQL just for reporting services...as it doesn't sound
like the product fulfills your needs.
I would not however, complain because the product doesn't fit my needs.
I would find a better product or be patient like the rest of us until
the next release which shall provide more functionality.
You make a lot of criticisms...most of which I have to read 3 times to
understand...and some of which are unfounded. Like ANY product, you are
going to have to find work arounds...as a developer you should know
this.
I have known many a bad developer...in a lot of circles I am problem
one of them...and they all blame their incompetence on the product.
One day there shall be a product that fulfills every need...and bad
developers won't have anything to complain about.
I can't wait for your next installment...as I am just about done with
my decoder.
Lukesql