I was having problems connecting to an OLAP database on the same domain as my IIS box, and read that adding a 'NETWORK' account may help resolve this. Somehow when it was added, no domain (specifically no 'NT AUTHORITY') was. Now I have an account with name 'NETWORK' but no domain. Every time I try to remove/delete this account, or do anything on the database withing Analysis Manager, it freezes. There is another database running on the same machine and we were able to add the NETWORK account with the domain 'NT AUTHORITY', and it is working fine, no freezing/lockups.
IIS is running on a Windows 2000 box with SP3 and Analysis Services w/ SP3a. The SQL Server is on a Windows 2003 Server, and Analysis Services w/ SP3a. Both machines have MDAC 2.8.
Is there any way to manually add the domain name to the account, or to remove it without using Analysis Manager? If you need any more information please let me know.
Thanks.Fixed. Had to go into the OlapObjects table and remove any relations to the NETWORK role. NOT RECOMMENDED because this can easily hose your db. After the Objects were removed we had to stop and start the Analysis Services service for it to take effect.
Originally posted by ArizonaBay
I was having problems connecting to an OLAP database on the same domain as my IIS box, and read that adding a 'NETWORK' account may help resolve this. Somehow when it was added, no domain (specifically no 'NT AUTHORITY') was. Now I have an account with name 'NETWORK' but no domain. Every time I try to remove/delete this account, or do anything on the database withing Analysis Manager, it freezes. There is another database running on the same machine and we were able to add the NETWORK account with the domain 'NT AUTHORITY', and it is working fine, no freezing/lockups.
IIS is running on a Windows 2000 box with SP3 and Analysis Services w/ SP3a. The SQL Server is on a Windows 2003 Server, and Analysis Services w/ SP3a. Both machines have MDAC 2.8.
Is there any way to manually add the domain name to the account, or to remove it without using Analysis Manager? If you need any more information please let me know.
Thanks.sql
Showing posts with label services. Show all posts
Showing posts with label services. Show all posts
Wednesday, March 28, 2012
Netscape Support
Can someone give me the status of Reporting Services support for
Netscape 7.1? I'm running sp1, and the report toolbar features
such as Export and Paging won't work in Netscape. Also
the formatting is all messed up. Books online
says Netscape 7.1 is supported- what's the deal?
Is there a patch or a workaround?
thanks,
Thomson Developer
Thomson LearningThere is a patch, and it is called IE6! ;-)))
"thomsonDeveloper" <thomsonDeveloper@.discussions.microsoft.com> wrote in
message news:4F568713-FFD2-42F0-B938-E43C0CD7441B@.microsoft.com...
> Can someone give me the status of Reporting Services support for
> Netscape 7.1? I'm running sp1, and the report toolbar features
> such as Export and Paging won't work in Netscape. Also
> the formatting is all messed up. Books online
> says Netscape 7.1 is supported- what's the deal?
> Is there a patch or a workaround?
> thanks,
> Thomson Developer
> Thomson Learning|||I'm not sure about the rest of you, but I consider Microsoft's lack of
support for Netscape / Mozilla / Opera a little shortsighted. What if you
plan on deploying to your outside clients? This will be a big issue. I
don't understand how keeping all of this IE specific helps MS or your
organization...
JD
On Fri, 22 Oct 2004 13:35:48 +0200, Marcus Phass wrote:
> There is a patch, and it is called IE6! ;-)))
> "thomsonDeveloper" <thomsonDeveloper@.discussions.microsoft.com> wrote in
> message news:4F568713-FFD2-42F0-B938-E43C0CD7441B@.microsoft.com...
>> Can someone give me the status of Reporting Services support for
>> Netscape 7.1? I'm running sp1, and the report toolbar features
>> such as Export and Paging won't work in Netscape. Also
>> the formatting is all messed up. Books online
>> says Netscape 7.1 is supported- what's the deal?
>> Is there a patch or a workaround?
>> thanks,
>> Thomson Developer
>> Thomson Learning|||Sorry Marcus but your answer is not good enough.
As a vendor I can not dictate to my clients which browser to use. In actual
fact I dont think that making the report viewer cross browser capable is a
lot of work but rather microsofts decision not to.
Reporting Services have so much potential to be a great solution but the
lack of plain simple RTF support and cross browser /platform support is 2
small issues that I rate extremly high for a basic report service.|||Simply I have a solution to the Netscape / Non IE browser
incompatibilites in the toolbar.
On the note of Netscape / Firefox / Safari support on Report Server it
has been nearly the bane on of my Reporting Services experience for the
last 5 months.
I have tried nearly everything possible to make Reporting Services WORK
Correctly with Netscape. (even at one point coming up with a hack to
have RS Load MY Javascript files instead of the ones MS Weeds into the
Resouces Files of the assembely)
The problem as most of you are aware (that are familiar with the
Netscape - Non -IE ) the MAIN Problem lies in the Toolbar
2 days ago I decided to resolve this once an for all, as I have a
client that uses all macs (safari and IE) And since Drill Down /
Export dosent work readily on Mac IE I had to do something drastic
(Although I do have a hack to make this work as well.
What I did was write my own toolbar component. The only thing it lacks
is the "FIND" And I doubt I will add it as nearly all our reports (Of
75 only 1 is multi page)
The neat part is it isnt a hack, its clean and slick , and Export
works, and Paging works , and Zoom works, on ANY Browser, better Yet I
am not using ANY Javascipt and it all works just fine with IE TOO !!!
Now all that said I have tried to think of what to do with what I have
come up with , since MS is too lazy (I'm pretty sure they simply choose
not to acknowledge other browsers as that would be some kind of
recognition or validation in the strange land of MS)
What I have done has value to me first of all, since I can now aside
from a very few cosmetic issues in NS deploy reports cross browser
without fear.
But does it have value (yes cash value) to others of you out there , as
either a custom control, or as a thrid party product ?
Or as some kind of source liscencing deal with other developers and
Reporting Services users ?
I have not seen this elsewhere and have looked and looked so I wrote
it, if you have interest in such an item drop me a line, or post here I
am curious to find out if there is interest.
Chris Wertman
Gideon wrote:
> Sorry Marcus but your answer is not good enough.
> As a vendor I can not dictate to my clients which browser to use. In
actual
> fact I dont think that making the report viewer cross browser capable
is a
> lot of work but rather microsofts decision not to.
> Reporting Services have so much potential to be a great solution but
the
> lack of plain simple RTF support and cross browser /platform support
is 2
> small issues that I rate extremly high for a basic report service.|||I would be interested in how you got it to work. I like to use quality apps first when available and why I use Firefox. I HAVE to use reporting services although the amount of problems I have run into it would have been far cheaper in the long run to have just purchased ActiveReports. In alot easier to develop reports with. sigh...
java_cruise
--
Message posted via http://www.sqlmonster.com|||Not to be terse, I am really not, but lots of reading.
And a little custom voddoo
Start with reading all the XML and URL Access info, I actually use a
combination webservice and HTML Utl access to get what I want and do
what I want, then mix those up, kill Cookie Based Sessions (This will
enable the drill down to work from with the frameset even on IE
(Without this it will only work on NS), Create a new frameset and do
some parsing of the report as it is being passed through the server to
capture (80% of the hard part) the pagecount for the pager to work.
I am prettying it up with a .Net 2.0 "Look" toolbar and I will post
some shots next week, I am also writing a custom FORM Based Security
mechanism for report based access that will work against the .Net 2.0
authentication provider (at least within a client)
I have seen and been mailed a ton of time on how I actually got mine to
work (the form based auth) so I figured I would post at least that, I
am still thinking if its better to provide it as a paid item, or charge
for it (It seems that even when I release something free I spend MORE
time supporting those who would implement it)
Chris
java cruise via SQLMonster.com wrote:
> I would be interested in how you got it to work. I like to use
quality apps first when available and why I use Firefox. I HAVE to use
reporting services although the amount of problems I have run into it
would have been far cheaper in the long run to have just purchased
ActiveReports. In alot easier to develop reports with. sigh...
>
> java_cruise
> --
> Message posted via http://www.sqlmonster.com|||Chris,
Were you able to fix the non-IE browser formatting issues as well as
the toolbar? We would be very interested in your solution if this is
the case.
TIA,
Greg
greg @. adsys dot com|||I didnt because it wast an issue for me.
You could "re-render" the report as it passes throught the toolbar (the
replacment toolbar) swapping out MS specific code that causes problems
in Netscape.
Generally for me at least the only thing that happens is the reports
get a little "squished" width wise , so when writing them I have the
report guys make em wider :)
Now we do only a very simple (visually) report thats are tables in a
grid like arrangment so I wouldnt know of other issues.
And like I said you could easily swap out the offending code at runtime
, assuming it is a tag or combination of tags that are casuing the
grief.
Chris
ghesla@.gmail.com wrote:
> Chris,
> Were you able to fix the non-IE browser formatting issues as well as
> the toolbar? We would be very interested in your solution if this is
> the case.
> TIA,
> Greg
> greg @. adsys dot com|||I didnt because it wast an issue for me.
You could "re-render" the report as it passes throught the toolbar (the
replacment toolbar) swapping out MS specific code that causes problems
in Netscape.
Generally for me at least the only thing that happens is the reports
get a little "squished" width wise , so when writing them I have the
report guys make em wider :)
Now we do only a very simple (visually) report thats are tables in a
grid like arrangment so I wouldnt know of other issues.
And like I said you could easily swap out the offending code at runtime
, assuming it is a tag or combination of tags that are casuing the
grief.
Chris
ghesla@.gmail.com wrote:
> Chris,
> Were you able to fix the non-IE browser formatting issues as well as
> the toolbar? We would be very interested in your solution if this is
> the case.
> TIA,
> Greg
> greg @. adsys dot com|||I am interested. If you can give me a proof of concept or demo of some sort,
we can talk money. I don't care to develop this nor am I all that interested
how it works, I'd just rather pay for it and be done with it.
"WertmanTheMad" wrote:
> Simply I have a solution to the Netscape / Non IE browser
> incompatibilites in the toolbar.
> On the note of Netscape / Firefox / Safari support on Report Server it
> has been nearly the bane on of my Reporting Services experience for the
> last 5 months.
> I have tried nearly everything possible to make Reporting Services WORK
> Correctly with Netscape. (even at one point coming up with a hack to
> have RS Load MY Javascript files instead of the ones MS Weeds into the
> Resouces Files of the assembely)
> The problem as most of you are aware (that are familiar with the
> Netscape - Non -IE ) the MAIN Problem lies in the Toolbar
> 2 days ago I decided to resolve this once an for all, as I have a
> client that uses all macs (safari and IE) And since Drill Down /
> Export dosent work readily on Mac IE I had to do something drastic
> (Although I do have a hack to make this work as well.
> What I did was write my own toolbar component. The only thing it lacks
> is the "FIND" And I doubt I will add it as nearly all our reports (Of
> 75 only 1 is multi page)
> The neat part is it isnt a hack, its clean and slick , and Export
> works, and Paging works , and Zoom works, on ANY Browser, better Yet I
> am not using ANY Javascipt and it all works just fine with IE TOO !!!
> Now all that said I have tried to think of what to do with what I have
> come up with , since MS is too lazy (I'm pretty sure they simply choose
> not to acknowledge other browsers as that would be some kind of
> recognition or validation in the strange land of MS)
> What I have done has value to me first of all, since I can now aside
> from a very few cosmetic issues in NS deploy reports cross browser
> without fear.
> But does it have value (yes cash value) to others of you out there , as
> either a custom control, or as a thrid party product ?
> Or as some kind of source liscencing deal with other developers and
> Reporting Services users ?
> I have not seen this elsewhere and have looked and looked so I wrote
> it, if you have interest in such an item drop me a line, or post here I
> am curious to find out if there is interest.
> Chris Wertman
>
>
>
>
> Gideon wrote:
> > Sorry Marcus but your answer is not good enough.
> >
> > As a vendor I can not dictate to my clients which browser to use. In
> actual
> > fact I dont think that making the report viewer cross browser capable
> is a
> > lot of work but rather microsofts decision not to.
> >
> > Reporting Services have so much potential to be a great solution but
> the
> > lack of plain simple RTF support and cross browser /platform support
> is 2
> > small issues that I rate extremly high for a basic report service.
>|||You can solve this by writing your own Rendering method. See the microsoft
link below.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_intro_1pia.asp
If the image get squished, write a small javascript to disable the style
attribute of images. It worked for me.
Kanchana Eramudugoda
"Eddie" wrote:
> I am interested. If you can give me a proof of concept or demo of some sort,
> we can talk money. I don't care to develop this nor am I all that interested
> how it works, I'd just rather pay for it and be done with it.
>
> "WertmanTheMad" wrote:
> > Simply I have a solution to the Netscape / Non IE browser
> > incompatibilites in the toolbar.
> >
> > On the note of Netscape / Firefox / Safari support on Report Server it
> > has been nearly the bane on of my Reporting Services experience for the
> > last 5 months.
> >
> > I have tried nearly everything possible to make Reporting Services WORK
> > Correctly with Netscape. (even at one point coming up with a hack to
> > have RS Load MY Javascript files instead of the ones MS Weeds into the
> > Resouces Files of the assembely)
> >
> > The problem as most of you are aware (that are familiar with the
> > Netscape - Non -IE ) the MAIN Problem lies in the Toolbar
> >
> > 2 days ago I decided to resolve this once an for all, as I have a
> > client that uses all macs (safari and IE) And since Drill Down /
> > Export dosent work readily on Mac IE I had to do something drastic
> > (Although I do have a hack to make this work as well.
> >
> > What I did was write my own toolbar component. The only thing it lacks
> > is the "FIND" And I doubt I will add it as nearly all our reports (Of
> > 75 only 1 is multi page)
> >
> > The neat part is it isnt a hack, its clean and slick , and Export
> > works, and Paging works , and Zoom works, on ANY Browser, better Yet I
> > am not using ANY Javascipt and it all works just fine with IE TOO !!!
> >
> > Now all that said I have tried to think of what to do with what I have
> > come up with , since MS is too lazy (I'm pretty sure they simply choose
> > not to acknowledge other browsers as that would be some kind of
> > recognition or validation in the strange land of MS)
> >
> > What I have done has value to me first of all, since I can now aside
> > from a very few cosmetic issues in NS deploy reports cross browser
> > without fear.
> >
> > But does it have value (yes cash value) to others of you out there , as
> > either a custom control, or as a thrid party product ?
> >
> > Or as some kind of source liscencing deal with other developers and
> > Reporting Services users ?
> >
> > I have not seen this elsewhere and have looked and looked so I wrote
> > it, if you have interest in such an item drop me a line, or post here I
> > am curious to find out if there is interest.
> >
> > Chris Wertman
> >
> >
> >
> >
> >
> >
> >
> >
> > Gideon wrote:
> > > Sorry Marcus but your answer is not good enough.
> > >
> > > As a vendor I can not dictate to my clients which browser to use. In
> > actual
> > > fact I dont think that making the report viewer cross browser capable
> > is a
> > > lot of work but rather microsofts decision not to.
> > >
> > > Reporting Services have so much potential to be a great solution but
> > the
> > > lack of plain simple RTF support and cross browser /platform support
> > is 2
> > > small issues that I rate extremly high for a basic report service.
> >
> >
Netscape 7.1? I'm running sp1, and the report toolbar features
such as Export and Paging won't work in Netscape. Also
the formatting is all messed up. Books online
says Netscape 7.1 is supported- what's the deal?
Is there a patch or a workaround?
thanks,
Thomson Developer
Thomson LearningThere is a patch, and it is called IE6! ;-)))
"thomsonDeveloper" <thomsonDeveloper@.discussions.microsoft.com> wrote in
message news:4F568713-FFD2-42F0-B938-E43C0CD7441B@.microsoft.com...
> Can someone give me the status of Reporting Services support for
> Netscape 7.1? I'm running sp1, and the report toolbar features
> such as Export and Paging won't work in Netscape. Also
> the formatting is all messed up. Books online
> says Netscape 7.1 is supported- what's the deal?
> Is there a patch or a workaround?
> thanks,
> Thomson Developer
> Thomson Learning|||I'm not sure about the rest of you, but I consider Microsoft's lack of
support for Netscape / Mozilla / Opera a little shortsighted. What if you
plan on deploying to your outside clients? This will be a big issue. I
don't understand how keeping all of this IE specific helps MS or your
organization...
JD
On Fri, 22 Oct 2004 13:35:48 +0200, Marcus Phass wrote:
> There is a patch, and it is called IE6! ;-)))
> "thomsonDeveloper" <thomsonDeveloper@.discussions.microsoft.com> wrote in
> message news:4F568713-FFD2-42F0-B938-E43C0CD7441B@.microsoft.com...
>> Can someone give me the status of Reporting Services support for
>> Netscape 7.1? I'm running sp1, and the report toolbar features
>> such as Export and Paging won't work in Netscape. Also
>> the formatting is all messed up. Books online
>> says Netscape 7.1 is supported- what's the deal?
>> Is there a patch or a workaround?
>> thanks,
>> Thomson Developer
>> Thomson Learning|||Sorry Marcus but your answer is not good enough.
As a vendor I can not dictate to my clients which browser to use. In actual
fact I dont think that making the report viewer cross browser capable is a
lot of work but rather microsofts decision not to.
Reporting Services have so much potential to be a great solution but the
lack of plain simple RTF support and cross browser /platform support is 2
small issues that I rate extremly high for a basic report service.|||Simply I have a solution to the Netscape / Non IE browser
incompatibilites in the toolbar.
On the note of Netscape / Firefox / Safari support on Report Server it
has been nearly the bane on of my Reporting Services experience for the
last 5 months.
I have tried nearly everything possible to make Reporting Services WORK
Correctly with Netscape. (even at one point coming up with a hack to
have RS Load MY Javascript files instead of the ones MS Weeds into the
Resouces Files of the assembely)
The problem as most of you are aware (that are familiar with the
Netscape - Non -IE ) the MAIN Problem lies in the Toolbar
2 days ago I decided to resolve this once an for all, as I have a
client that uses all macs (safari and IE) And since Drill Down /
Export dosent work readily on Mac IE I had to do something drastic
(Although I do have a hack to make this work as well.
What I did was write my own toolbar component. The only thing it lacks
is the "FIND" And I doubt I will add it as nearly all our reports (Of
75 only 1 is multi page)
The neat part is it isnt a hack, its clean and slick , and Export
works, and Paging works , and Zoom works, on ANY Browser, better Yet I
am not using ANY Javascipt and it all works just fine with IE TOO !!!
Now all that said I have tried to think of what to do with what I have
come up with , since MS is too lazy (I'm pretty sure they simply choose
not to acknowledge other browsers as that would be some kind of
recognition or validation in the strange land of MS)
What I have done has value to me first of all, since I can now aside
from a very few cosmetic issues in NS deploy reports cross browser
without fear.
But does it have value (yes cash value) to others of you out there , as
either a custom control, or as a thrid party product ?
Or as some kind of source liscencing deal with other developers and
Reporting Services users ?
I have not seen this elsewhere and have looked and looked so I wrote
it, if you have interest in such an item drop me a line, or post here I
am curious to find out if there is interest.
Chris Wertman
Gideon wrote:
> Sorry Marcus but your answer is not good enough.
> As a vendor I can not dictate to my clients which browser to use. In
actual
> fact I dont think that making the report viewer cross browser capable
is a
> lot of work but rather microsofts decision not to.
> Reporting Services have so much potential to be a great solution but
the
> lack of plain simple RTF support and cross browser /platform support
is 2
> small issues that I rate extremly high for a basic report service.|||I would be interested in how you got it to work. I like to use quality apps first when available and why I use Firefox. I HAVE to use reporting services although the amount of problems I have run into it would have been far cheaper in the long run to have just purchased ActiveReports. In alot easier to develop reports with. sigh...
java_cruise
--
Message posted via http://www.sqlmonster.com|||Not to be terse, I am really not, but lots of reading.
And a little custom voddoo
Start with reading all the XML and URL Access info, I actually use a
combination webservice and HTML Utl access to get what I want and do
what I want, then mix those up, kill Cookie Based Sessions (This will
enable the drill down to work from with the frameset even on IE
(Without this it will only work on NS), Create a new frameset and do
some parsing of the report as it is being passed through the server to
capture (80% of the hard part) the pagecount for the pager to work.
I am prettying it up with a .Net 2.0 "Look" toolbar and I will post
some shots next week, I am also writing a custom FORM Based Security
mechanism for report based access that will work against the .Net 2.0
authentication provider (at least within a client)
I have seen and been mailed a ton of time on how I actually got mine to
work (the form based auth) so I figured I would post at least that, I
am still thinking if its better to provide it as a paid item, or charge
for it (It seems that even when I release something free I spend MORE
time supporting those who would implement it)
Chris
java cruise via SQLMonster.com wrote:
> I would be interested in how you got it to work. I like to use
quality apps first when available and why I use Firefox. I HAVE to use
reporting services although the amount of problems I have run into it
would have been far cheaper in the long run to have just purchased
ActiveReports. In alot easier to develop reports with. sigh...
>
> java_cruise
> --
> Message posted via http://www.sqlmonster.com|||Chris,
Were you able to fix the non-IE browser formatting issues as well as
the toolbar? We would be very interested in your solution if this is
the case.
TIA,
Greg
greg @. adsys dot com|||I didnt because it wast an issue for me.
You could "re-render" the report as it passes throught the toolbar (the
replacment toolbar) swapping out MS specific code that causes problems
in Netscape.
Generally for me at least the only thing that happens is the reports
get a little "squished" width wise , so when writing them I have the
report guys make em wider :)
Now we do only a very simple (visually) report thats are tables in a
grid like arrangment so I wouldnt know of other issues.
And like I said you could easily swap out the offending code at runtime
, assuming it is a tag or combination of tags that are casuing the
grief.
Chris
ghesla@.gmail.com wrote:
> Chris,
> Were you able to fix the non-IE browser formatting issues as well as
> the toolbar? We would be very interested in your solution if this is
> the case.
> TIA,
> Greg
> greg @. adsys dot com|||I didnt because it wast an issue for me.
You could "re-render" the report as it passes throught the toolbar (the
replacment toolbar) swapping out MS specific code that causes problems
in Netscape.
Generally for me at least the only thing that happens is the reports
get a little "squished" width wise , so when writing them I have the
report guys make em wider :)
Now we do only a very simple (visually) report thats are tables in a
grid like arrangment so I wouldnt know of other issues.
And like I said you could easily swap out the offending code at runtime
, assuming it is a tag or combination of tags that are casuing the
grief.
Chris
ghesla@.gmail.com wrote:
> Chris,
> Were you able to fix the non-IE browser formatting issues as well as
> the toolbar? We would be very interested in your solution if this is
> the case.
> TIA,
> Greg
> greg @. adsys dot com|||I am interested. If you can give me a proof of concept or demo of some sort,
we can talk money. I don't care to develop this nor am I all that interested
how it works, I'd just rather pay for it and be done with it.
"WertmanTheMad" wrote:
> Simply I have a solution to the Netscape / Non IE browser
> incompatibilites in the toolbar.
> On the note of Netscape / Firefox / Safari support on Report Server it
> has been nearly the bane on of my Reporting Services experience for the
> last 5 months.
> I have tried nearly everything possible to make Reporting Services WORK
> Correctly with Netscape. (even at one point coming up with a hack to
> have RS Load MY Javascript files instead of the ones MS Weeds into the
> Resouces Files of the assembely)
> The problem as most of you are aware (that are familiar with the
> Netscape - Non -IE ) the MAIN Problem lies in the Toolbar
> 2 days ago I decided to resolve this once an for all, as I have a
> client that uses all macs (safari and IE) And since Drill Down /
> Export dosent work readily on Mac IE I had to do something drastic
> (Although I do have a hack to make this work as well.
> What I did was write my own toolbar component. The only thing it lacks
> is the "FIND" And I doubt I will add it as nearly all our reports (Of
> 75 only 1 is multi page)
> The neat part is it isnt a hack, its clean and slick , and Export
> works, and Paging works , and Zoom works, on ANY Browser, better Yet I
> am not using ANY Javascipt and it all works just fine with IE TOO !!!
> Now all that said I have tried to think of what to do with what I have
> come up with , since MS is too lazy (I'm pretty sure they simply choose
> not to acknowledge other browsers as that would be some kind of
> recognition or validation in the strange land of MS)
> What I have done has value to me first of all, since I can now aside
> from a very few cosmetic issues in NS deploy reports cross browser
> without fear.
> But does it have value (yes cash value) to others of you out there , as
> either a custom control, or as a thrid party product ?
> Or as some kind of source liscencing deal with other developers and
> Reporting Services users ?
> I have not seen this elsewhere and have looked and looked so I wrote
> it, if you have interest in such an item drop me a line, or post here I
> am curious to find out if there is interest.
> Chris Wertman
>
>
>
>
> Gideon wrote:
> > Sorry Marcus but your answer is not good enough.
> >
> > As a vendor I can not dictate to my clients which browser to use. In
> actual
> > fact I dont think that making the report viewer cross browser capable
> is a
> > lot of work but rather microsofts decision not to.
> >
> > Reporting Services have so much potential to be a great solution but
> the
> > lack of plain simple RTF support and cross browser /platform support
> is 2
> > small issues that I rate extremly high for a basic report service.
>|||You can solve this by writing your own Rendering method. See the microsoft
link below.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSPROG/htm/rsp_prog_intro_1pia.asp
If the image get squished, write a small javascript to disable the style
attribute of images. It worked for me.
Kanchana Eramudugoda
"Eddie" wrote:
> I am interested. If you can give me a proof of concept or demo of some sort,
> we can talk money. I don't care to develop this nor am I all that interested
> how it works, I'd just rather pay for it and be done with it.
>
> "WertmanTheMad" wrote:
> > Simply I have a solution to the Netscape / Non IE browser
> > incompatibilites in the toolbar.
> >
> > On the note of Netscape / Firefox / Safari support on Report Server it
> > has been nearly the bane on of my Reporting Services experience for the
> > last 5 months.
> >
> > I have tried nearly everything possible to make Reporting Services WORK
> > Correctly with Netscape. (even at one point coming up with a hack to
> > have RS Load MY Javascript files instead of the ones MS Weeds into the
> > Resouces Files of the assembely)
> >
> > The problem as most of you are aware (that are familiar with the
> > Netscape - Non -IE ) the MAIN Problem lies in the Toolbar
> >
> > 2 days ago I decided to resolve this once an for all, as I have a
> > client that uses all macs (safari and IE) And since Drill Down /
> > Export dosent work readily on Mac IE I had to do something drastic
> > (Although I do have a hack to make this work as well.
> >
> > What I did was write my own toolbar component. The only thing it lacks
> > is the "FIND" And I doubt I will add it as nearly all our reports (Of
> > 75 only 1 is multi page)
> >
> > The neat part is it isnt a hack, its clean and slick , and Export
> > works, and Paging works , and Zoom works, on ANY Browser, better Yet I
> > am not using ANY Javascipt and it all works just fine with IE TOO !!!
> >
> > Now all that said I have tried to think of what to do with what I have
> > come up with , since MS is too lazy (I'm pretty sure they simply choose
> > not to acknowledge other browsers as that would be some kind of
> > recognition or validation in the strange land of MS)
> >
> > What I have done has value to me first of all, since I can now aside
> > from a very few cosmetic issues in NS deploy reports cross browser
> > without fear.
> >
> > But does it have value (yes cash value) to others of you out there , as
> > either a custom control, or as a thrid party product ?
> >
> > Or as some kind of source liscencing deal with other developers and
> > Reporting Services users ?
> >
> > I have not seen this elsewhere and have looked and looked so I wrote
> > it, if you have interest in such an item drop me a line, or post here I
> > am curious to find out if there is interest.
> >
> > Chris Wertman
> >
> >
> >
> >
> >
> >
> >
> >
> > Gideon wrote:
> > > Sorry Marcus but your answer is not good enough.
> > >
> > > As a vendor I can not dictate to my clients which browser to use. In
> > actual
> > > fact I dont think that making the report viewer cross browser capable
> > is a
> > > lot of work but rather microsofts decision not to.
> > >
> > > Reporting Services have so much potential to be a great solution but
> > the
> > > lack of plain simple RTF support and cross browser /platform support
> > is 2
> > > small issues that I rate extremly high for a basic report service.
> >
> >
NETSCAPE and IFRAME problem
I have a report that works perfectly in IE but the iframe doesn't show up at
all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services supports).
I've tried everything to get it to show from including ID and NAME
attributes in the iframe tag in the ReportViewer component, to setting all
visibles to true...Nothing is working and I need a resolution ASAP, I've
seen other developers in this forum and on the web with similar problems
with RS in Netscape.
Here is the ReportViewer tag in the aspx source code:
<cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
Format="Default"></cc1:reportviewer>
Here is the code that builds the iframe in the ReportViewer component:
output.WriteBeginTag("iframe")
output.WriteAttribute("id", Me.ID)
output.WriteAttribute("name", Me.ID)
output.WriteAttribute("src", Me.BuildUrlString())
output.WriteAttribute("width", Me.Width.ToString())
output.WriteAttribute("height", Me.Height.ToString())
output.WriteAttribute("style", "border: 1 solid #C0C0C0")
output.WriteAttribute("border", "0")
output.WriteAttribute("frameborder", "0")
output.Write(HtmlTextWriter.TagRightChar)
output.WriteEndTag("iframe")
output.WriteLine()
Here is the iframe tag copied right from the page source when it loads:
<iframe id="ReportViewer1" name="ReportViewer1"
src="http://pics.10026.com/?src=http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
height="95%" style="border: 1 solid #C0C0C0" border="0"
frameborder="0"></iframe>
The iframe code is there in the source but nothing is showing up in the
browser. Any help would be greatly appreciated. Thank you.
MarkI was told MS is not going to support Netscape if HTML 4.0
They are planning on changing there documentation to reflect this.
Try rendering in PDF. Acrobat reader gives you the navigation from page to
page and the html links work as well.
"Mark" <markkosokovits@.hotmail.com> wrote in message
news:Of7g9q7fEHA.4040@.TK2MSFTNGP10.phx.gbl...
> I have a report that works perfectly in IE but the iframe doesn't show up
at
> all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services
supports).
> I've tried everything to get it to show from including ID and NAME
> attributes in the iframe tag in the ReportViewer component, to setting all
> visibles to true...Nothing is working and I need a resolution ASAP, I've
> seen other developers in this forum and on the web with similar problems
> with RS in Netscape.
> Here is the ReportViewer tag in the aspx source code:
> <cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
> Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
> Format="Default"></cc1:reportviewer>
> Here is the code that builds the iframe in the ReportViewer component:
> output.WriteBeginTag("iframe")
> output.WriteAttribute("id", Me.ID)
> output.WriteAttribute("name", Me.ID)
> output.WriteAttribute("src", Me.BuildUrlString())
> output.WriteAttribute("width", Me.Width.ToString())
> output.WriteAttribute("height", Me.Height.ToString())
> output.WriteAttribute("style", "border: 1 solid #C0C0C0")
> output.WriteAttribute("border", "0")
> output.WriteAttribute("frameborder", "0")
> output.Write(HtmlTextWriter.TagRightChar)
> output.WriteEndTag("iframe")
> output.WriteLine()
> Here is the iframe tag copied right from the page source when it loads:
> <iframe id="ReportViewer1" name="ReportViewer1"
>
src="http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
>
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
> ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
> height="95%" style="border: 1 solid #C0C0C0" border="0"
> frameborder="0"></iframe>
> The iframe code is there in the source but nothing is showing up in the
> browser. Any help would be greatly appreciated. Thank you.
> Mark
>|||Check out Microsoft's RS example named Product Catalog in Netscape 7.1.
MS seem to be having the same problems.
"Mark" <markkosokovits@.hotmail.com> wrote in message
news:Of7g9q7fEHA.4040@.TK2MSFTNGP10.phx.gbl...
> I have a report that works perfectly in IE but the iframe doesn't show up
at
> all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services
supports).
> I've tried everything to get it to show from including ID and NAME
> attributes in the iframe tag in the ReportViewer component, to setting all
> visibles to true...Nothing is working and I need a resolution ASAP, I've
> seen other developers in this forum and on the web with similar problems
> with RS in Netscape.
> Here is the ReportViewer tag in the aspx source code:
> <cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
> Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
> Format="Default"></cc1:reportviewer>
> Here is the code that builds the iframe in the ReportViewer component:
> output.WriteBeginTag("iframe")
> output.WriteAttribute("id", Me.ID)
> output.WriteAttribute("name", Me.ID)
> output.WriteAttribute("src", Me.BuildUrlString())
> output.WriteAttribute("width", Me.Width.ToString())
> output.WriteAttribute("height", Me.Height.ToString())
> output.WriteAttribute("style", "border: 1 solid #C0C0C0")
> output.WriteAttribute("border", "0")
> output.WriteAttribute("frameborder", "0")
> output.Write(HtmlTextWriter.TagRightChar)
> output.WriteEndTag("iframe")
> output.WriteLine()
> Here is the iframe tag copied right from the page source when it loads:
> <iframe id="ReportViewer1" name="ReportViewer1"
>
src="http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
>
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
> ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
> height="95%" style="border: 1 solid #C0C0C0" border="0"
> frameborder="0"></iframe>
> The iframe code is there in the source but nothing is showing up in the
> browser. Any help would be greatly appreciated. Thank you.
> Mark
>|||Thanks for the suggestion but the client wants the ability to copy and paste
sections from the report to another application, and PDF doesn't let you
c&p...
".Net Report Dev" <aanargyros@.hotmail.com> wrote in message
news:u$hUAh8fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> I was told MS is not going to support Netscape if HTML 4.0
> They are planning on changing there documentation to reflect this.
> Try rendering in PDF. Acrobat reader gives you the navigation from page
to
> page and the html links work as well.
>
> "Mark" <markkosokovits@.hotmail.com> wrote in message
> news:Of7g9q7fEHA.4040@.TK2MSFTNGP10.phx.gbl...
> > I have a report that works perfectly in IE but the iframe doesn't show
up
> at
> > all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services
> supports).
> > I've tried everything to get it to show from including ID and NAME
> > attributes in the iframe tag in the ReportViewer component, to setting
all
> > visibles to true...Nothing is working and I need a resolution ASAP, I've
> > seen other developers in this forum and on the web with similar problems
> > with RS in Netscape.
> >
> > Here is the ReportViewer tag in the aspx source code:
> >
> > <cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
> > Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
> > Format="Default"></cc1:reportviewer>
> >
> > Here is the code that builds the iframe in the ReportViewer component:
> >
> > output.WriteBeginTag("iframe")
> > output.WriteAttribute("id", Me.ID)
> > output.WriteAttribute("name", Me.ID)
> > output.WriteAttribute("src", Me.BuildUrlString())
> > output.WriteAttribute("width", Me.Width.ToString())
> > output.WriteAttribute("height", Me.Height.ToString())
> > output.WriteAttribute("style", "border: 1 solid #C0C0C0")
> > output.WriteAttribute("border", "0")
> > output.WriteAttribute("frameborder", "0")
> > output.Write(HtmlTextWriter.TagRightChar)
> > output.WriteEndTag("iframe")
> > output.WriteLine()
> >
> > Here is the iframe tag copied right from the page source when it loads:
> >
> > <iframe id="ReportViewer1" name="ReportViewer1"
> >
>
src="http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
> >
>
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
> > ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
> > height="95%" style="border: 1 solid #C0C0C0" border="0"
> > frameborder="0"></iframe>
> >
> > The iframe code is there in the source but nothing is showing up in the
> > browser. Any help would be greatly appreciated. Thank you.
> >
> > Mark
> >
> >
>
all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services supports).
I've tried everything to get it to show from including ID and NAME
attributes in the iframe tag in the ReportViewer component, to setting all
visibles to true...Nothing is working and I need a resolution ASAP, I've
seen other developers in this forum and on the web with similar problems
with RS in Netscape.
Here is the ReportViewer tag in the aspx source code:
<cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
Format="Default"></cc1:reportviewer>
Here is the code that builds the iframe in the ReportViewer component:
output.WriteBeginTag("iframe")
output.WriteAttribute("id", Me.ID)
output.WriteAttribute("name", Me.ID)
output.WriteAttribute("src", Me.BuildUrlString())
output.WriteAttribute("width", Me.Width.ToString())
output.WriteAttribute("height", Me.Height.ToString())
output.WriteAttribute("style", "border: 1 solid #C0C0C0")
output.WriteAttribute("border", "0")
output.WriteAttribute("frameborder", "0")
output.Write(HtmlTextWriter.TagRightChar)
output.WriteEndTag("iframe")
output.WriteLine()
Here is the iframe tag copied right from the page source when it loads:
<iframe id="ReportViewer1" name="ReportViewer1"
src="http://pics.10026.com/?src=http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
height="95%" style="border: 1 solid #C0C0C0" border="0"
frameborder="0"></iframe>
The iframe code is there in the source but nothing is showing up in the
browser. Any help would be greatly appreciated. Thank you.
MarkI was told MS is not going to support Netscape if HTML 4.0
They are planning on changing there documentation to reflect this.
Try rendering in PDF. Acrobat reader gives you the navigation from page to
page and the html links work as well.
"Mark" <markkosokovits@.hotmail.com> wrote in message
news:Of7g9q7fEHA.4040@.TK2MSFTNGP10.phx.gbl...
> I have a report that works perfectly in IE but the iframe doesn't show up
at
> all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services
supports).
> I've tried everything to get it to show from including ID and NAME
> attributes in the iframe tag in the ReportViewer component, to setting all
> visibles to true...Nothing is working and I need a resolution ASAP, I've
> seen other developers in this forum and on the web with similar problems
> with RS in Netscape.
> Here is the ReportViewer tag in the aspx source code:
> <cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
> Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
> Format="Default"></cc1:reportviewer>
> Here is the code that builds the iframe in the ReportViewer component:
> output.WriteBeginTag("iframe")
> output.WriteAttribute("id", Me.ID)
> output.WriteAttribute("name", Me.ID)
> output.WriteAttribute("src", Me.BuildUrlString())
> output.WriteAttribute("width", Me.Width.ToString())
> output.WriteAttribute("height", Me.Height.ToString())
> output.WriteAttribute("style", "border: 1 solid #C0C0C0")
> output.WriteAttribute("border", "0")
> output.WriteAttribute("frameborder", "0")
> output.Write(HtmlTextWriter.TagRightChar)
> output.WriteEndTag("iframe")
> output.WriteLine()
> Here is the iframe tag copied right from the page source when it loads:
> <iframe id="ReportViewer1" name="ReportViewer1"
>
src="http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
>
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
> ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
> height="95%" style="border: 1 solid #C0C0C0" border="0"
> frameborder="0"></iframe>
> The iframe code is there in the source but nothing is showing up in the
> browser. Any help would be greatly appreciated. Thank you.
> Mark
>|||Check out Microsoft's RS example named Product Catalog in Netscape 7.1.
MS seem to be having the same problems.
"Mark" <markkosokovits@.hotmail.com> wrote in message
news:Of7g9q7fEHA.4040@.TK2MSFTNGP10.phx.gbl...
> I have a report that works perfectly in IE but the iframe doesn't show up
at
> all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services
supports).
> I've tried everything to get it to show from including ID and NAME
> attributes in the iframe tag in the ReportViewer component, to setting all
> visibles to true...Nothing is working and I need a resolution ASAP, I've
> seen other developers in this forum and on the web with similar problems
> with RS in Netscape.
> Here is the ReportViewer tag in the aspx source code:
> <cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
> Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
> Format="Default"></cc1:reportviewer>
> Here is the code that builds the iframe in the ReportViewer component:
> output.WriteBeginTag("iframe")
> output.WriteAttribute("id", Me.ID)
> output.WriteAttribute("name", Me.ID)
> output.WriteAttribute("src", Me.BuildUrlString())
> output.WriteAttribute("width", Me.Width.ToString())
> output.WriteAttribute("height", Me.Height.ToString())
> output.WriteAttribute("style", "border: 1 solid #C0C0C0")
> output.WriteAttribute("border", "0")
> output.WriteAttribute("frameborder", "0")
> output.Write(HtmlTextWriter.TagRightChar)
> output.WriteEndTag("iframe")
> output.WriteLine()
> Here is the iframe tag copied right from the page source when it loads:
> <iframe id="ReportViewer1" name="ReportViewer1"
>
src="http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
>
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
> ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
> height="95%" style="border: 1 solid #C0C0C0" border="0"
> frameborder="0"></iframe>
> The iframe code is there in the source but nothing is showing up in the
> browser. Any help would be greatly appreciated. Thank you.
> Mark
>|||Thanks for the suggestion but the client wants the ability to copy and paste
sections from the report to another application, and PDF doesn't let you
c&p...
".Net Report Dev" <aanargyros@.hotmail.com> wrote in message
news:u$hUAh8fEHA.3024@.TK2MSFTNGP10.phx.gbl...
> I was told MS is not going to support Netscape if HTML 4.0
> They are planning on changing there documentation to reflect this.
> Try rendering in PDF. Acrobat reader gives you the navigation from page
to
> page and the html links work as well.
>
> "Mark" <markkosokovits@.hotmail.com> wrote in message
> news:Of7g9q7fEHA.4040@.TK2MSFTNGP10.phx.gbl...
> > I have a report that works perfectly in IE but the iframe doesn't show
up
> at
> > all in Netscape 6, 7, and 7.1 (which Microsoft Reporting Services
> supports).
> > I've tried everything to get it to show from including ID and NAME
> > attributes in the iframe tag in the ReportViewer component, to setting
all
> > visibles to true...Nothing is working and I need a resolution ASAP, I've
> > seen other developers in this forum and on the web with similar problems
> > with RS in Netscape.
> >
> > Here is the ReportViewer tag in the aspx source code:
> >
> > <cc1:reportviewer id="ReportViewer1" name="ReportViewer1" runat="server"
> > Height="95%" Width="100%" BorderStyle="None" Visible="TRUE"
> > Format="Default"></cc1:reportviewer>
> >
> > Here is the code that builds the iframe in the ReportViewer component:
> >
> > output.WriteBeginTag("iframe")
> > output.WriteAttribute("id", Me.ID)
> > output.WriteAttribute("name", Me.ID)
> > output.WriteAttribute("src", Me.BuildUrlString())
> > output.WriteAttribute("width", Me.Width.ToString())
> > output.WriteAttribute("height", Me.Height.ToString())
> > output.WriteAttribute("style", "border: 1 solid #C0C0C0")
> > output.WriteAttribute("border", "0")
> > output.WriteAttribute("frameborder", "0")
> > output.Write(HtmlTextWriter.TagRightChar)
> > output.WriteEndTag("iframe")
> > output.WriteLine()
> >
> > Here is the iframe tag copied right from the page source when it loads:
> >
> > <iframe id="ReportViewer1" name="ReportViewer1"
> >
>
src="http://localhost/ReportServer?/Reporting/Report_Full&rc:Stylesheet=SC_S
> >
>
tyles&rs:Command=Render&ClientID=10&EventNumber=All&rc:parameters=false&endD
> > ate=8/11/2004&startDate=7/25/2004&rs:Format=HTML4.0" width="100%"
> > height="95%" style="border: 1 solid #C0C0C0" border="0"
> > frameborder="0"></iframe>
> >
> > The iframe code is there in the source but nothing is showing up in the
> > browser. Any help would be greatly appreciated. Thank you.
> >
> > Mark
> >
> >
>
Monday, March 26, 2012
NET2 and Reporting Services
Is it possible to get Reporting Services running on a server wtih .NET2 beta1
installed?
thanksNot sure if order of install makes a difference but right now i'm
running XP Pro SP1, VS2002, VS2003, .NET1.0, .NET1.1, and .NET2.0 on
my machine with reporting services and i have no probs. .NET 2.0 was
the last thing i installed.
"marv" <marv@.discussions.microsoft.com> wrote in message news:<45C73938-019C-4402-A50D-87B6510CF5C8@.microsoft.com>...
> Is it possible to get Reporting Services running on a server wtih .NET2 beta1
> installed?
> thanks
installed?
thanksNot sure if order of install makes a difference but right now i'm
running XP Pro SP1, VS2002, VS2003, .NET1.0, .NET1.1, and .NET2.0 on
my machine with reporting services and i have no probs. .NET 2.0 was
the last thing i installed.
"marv" <marv@.discussions.microsoft.com> wrote in message news:<45C73938-019C-4402-A50D-87B6510CF5C8@.microsoft.com>...
> Is it possible to get Reporting Services running on a server wtih .NET2 beta1
> installed?
> thanks
Wednesday, March 7, 2012
needs 2 download Reporting services
i have sql server 2005 but didn't have reporting services can anyone tell me link where from i can download sql server 2005 reporting services server
If you have a SKU that has RS integrated then it is part of the install process for SQLServer, you get to select RS when going through the install wizard.
Needing to run reporting services on SQL Server 2000
Hi
I want to install SQL Server 2000 Enterprise Edition on Windows XP but it isn't installing.
I have installed SQL Server 2000 Personal Edition but Reporting Services are not installing on the server.
PLZ some one help me out.
SQL 2000 Enterprise Edition is not supported on XP. Please see this link for requirements:
http://www.microsoft.com/sql/prodinfo/previousversions/system-requirements.mspx
Thanks,
Sam Lester (MSFT)
Needed: Feature chart by Reporting Services Edition
I will be grateful to anyone who can tell me where to find a clear,
comprehensive explanation of what features of Reporting Services are
available in which edition(s) of Reporting Services.
I'm using Reporting Services 2005.
After much searching/experimenting, I now know 2 things:
--A "scale-out deployment" is not supported in the Standard version
(this also appears to mean that the encryption keys are useless on
any but the original machine -- so disaster recovery is problematic)
--"Click through" reports, via Report Builder type reports, are not available
in the Standard version.
It certainly is a time-drain to discover and verify these things one at a
time.
Assistance would be greatly appreciated (and anticipated from Microsoft).
--Dana Forsberg
P.S. Among other things, I have looked around quite a bit starting from:
ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/rptsrvr9/html/b8d18d3d-9db0-43e7-8286-7b46cc3a37ed.htm
That seems a comprehensive "root" to a lot of resources -- but if there's a
feature chart by Edition, it has eluded me so far.I googled: reporting services features
First hit is this:
http://www.microsoft.com/sql/technologies/reporting/default.mspx
On this page is this link:
http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Dana Forsberg" <DanaForsberg@.discussions.microsoft.com> wrote in message
news:4CE62965-65E6-41B6-9FE4-CF77EF49A7A2@.microsoft.com...
>I will be grateful to anyone who can tell me where to find a clear,
> comprehensive explanation of what features of Reporting Services are
> available in which edition(s) of Reporting Services.
> I'm using Reporting Services 2005.
> After much searching/experimenting, I now know 2 things:
> --A "scale-out deployment" is not supported in the Standard version
> (this also appears to mean that the encryption keys are useless on
> any but the original machine -- so disaster recovery is problematic)
> --"Click through" reports, via Report Builder type reports, are not
> available
> in the Standard version.
> It certainly is a time-drain to discover and verify these things one at a
> time.
> Assistance would be greatly appreciated (and anticipated from Microsoft).
> --Dana Forsberg
> P.S. Among other things, I have looked around quite a bit starting from:
> ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/rptsrvr9/html/b8d18d3d-9db0-43e7-8286-7b46cc3a37ed.htm
> That seems a comprehensive "root" to a lot of resources -- but if there's
> a
> feature chart by Edition, it has eluded me so far.
>|||Thank you for a very timely and on-target reply.
I really appreciate it.
And... is "Infinite Click-through" the same thing as "Click through reports"?
Actually, I just did a search and found out that it is -- but please pass on
a vote for a little "blurb" of explanation on feature charts, rather than the
austere case of only one or two words to guess from, identifying a given
feature.
Again, thanks very much for the reply.
"Bruce L-C [MVP]" wrote:
> I googled: reporting services features
> First hit is this:
> http://www.microsoft.com/sql/technologies/reporting/default.mspx
> On this page is this link:
> http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Dana Forsberg" <DanaForsberg@.discussions.microsoft.com> wrote in message
> news:4CE62965-65E6-41B6-9FE4-CF77EF49A7A2@.microsoft.com...
> >I will be grateful to anyone who can tell me where to find a clear,
> > comprehensive explanation of what features of Reporting Services are
> > available in which edition(s) of Reporting Services.
> >
> > I'm using Reporting Services 2005.
> > After much searching/experimenting, I now know 2 things:
> > --A "scale-out deployment" is not supported in the Standard version
> > (this also appears to mean that the encryption keys are useless on
> > any but the original machine -- so disaster recovery is problematic)
> >
> > --"Click through" reports, via Report Builder type reports, are not
> > available
> > in the Standard version.
> >
> > It certainly is a time-drain to discover and verify these things one at a
> > time.
> >
> > Assistance would be greatly appreciated (and anticipated from Microsoft).
> >
> > --Dana Forsberg
> >
> > P.S. Among other things, I have looked around quite a bit starting from:
> > ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/rptsrvr9/html/b8d18d3d-9db0-43e7-8286-7b46cc3a37ed.htm
> >
> > That seems a comprehensive "root" to a lot of resources -- but if there's
> > a
> > feature chart by Edition, it has eluded me so far.
> >
>
>
comprehensive explanation of what features of Reporting Services are
available in which edition(s) of Reporting Services.
I'm using Reporting Services 2005.
After much searching/experimenting, I now know 2 things:
--A "scale-out deployment" is not supported in the Standard version
(this also appears to mean that the encryption keys are useless on
any but the original machine -- so disaster recovery is problematic)
--"Click through" reports, via Report Builder type reports, are not available
in the Standard version.
It certainly is a time-drain to discover and verify these things one at a
time.
Assistance would be greatly appreciated (and anticipated from Microsoft).
--Dana Forsberg
P.S. Among other things, I have looked around quite a bit starting from:
ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/rptsrvr9/html/b8d18d3d-9db0-43e7-8286-7b46cc3a37ed.htm
That seems a comprehensive "root" to a lot of resources -- but if there's a
feature chart by Edition, it has eluded me so far.I googled: reporting services features
First hit is this:
http://www.microsoft.com/sql/technologies/reporting/default.mspx
On this page is this link:
http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Dana Forsberg" <DanaForsberg@.discussions.microsoft.com> wrote in message
news:4CE62965-65E6-41B6-9FE4-CF77EF49A7A2@.microsoft.com...
>I will be grateful to anyone who can tell me where to find a clear,
> comprehensive explanation of what features of Reporting Services are
> available in which edition(s) of Reporting Services.
> I'm using Reporting Services 2005.
> After much searching/experimenting, I now know 2 things:
> --A "scale-out deployment" is not supported in the Standard version
> (this also appears to mean that the encryption keys are useless on
> any but the original machine -- so disaster recovery is problematic)
> --"Click through" reports, via Report Builder type reports, are not
> available
> in the Standard version.
> It certainly is a time-drain to discover and verify these things one at a
> time.
> Assistance would be greatly appreciated (and anticipated from Microsoft).
> --Dana Forsberg
> P.S. Among other things, I have looked around quite a bit starting from:
> ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/rptsrvr9/html/b8d18d3d-9db0-43e7-8286-7b46cc3a37ed.htm
> That seems a comprehensive "root" to a lot of resources -- but if there's
> a
> feature chart by Edition, it has eluded me so far.
>|||Thank you for a very timely and on-target reply.
I really appreciate it.
And... is "Infinite Click-through" the same thing as "Click through reports"?
Actually, I just did a search and found out that it is -- but please pass on
a vote for a little "blurb" of explanation on feature charts, rather than the
austere case of only one or two words to guess from, identifying a given
feature.
Again, thanks very much for the reply.
"Bruce L-C [MVP]" wrote:
> I googled: reporting services features
> First hit is this:
> http://www.microsoft.com/sql/technologies/reporting/default.mspx
> On this page is this link:
> http://www.microsoft.com/sql/technologies/reporting/rsfeatures.mspx
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Dana Forsberg" <DanaForsberg@.discussions.microsoft.com> wrote in message
> news:4CE62965-65E6-41B6-9FE4-CF77EF49A7A2@.microsoft.com...
> >I will be grateful to anyone who can tell me where to find a clear,
> > comprehensive explanation of what features of Reporting Services are
> > available in which edition(s) of Reporting Services.
> >
> > I'm using Reporting Services 2005.
> > After much searching/experimenting, I now know 2 things:
> > --A "scale-out deployment" is not supported in the Standard version
> > (this also appears to mean that the encryption keys are useless on
> > any but the original machine -- so disaster recovery is problematic)
> >
> > --"Click through" reports, via Report Builder type reports, are not
> > available
> > in the Standard version.
> >
> > It certainly is a time-drain to discover and verify these things one at a
> > time.
> >
> > Assistance would be greatly appreciated (and anticipated from Microsoft).
> >
> > --Dana Forsberg
> >
> > P.S. Among other things, I have looked around quite a bit starting from:
> > ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/rptsrvr9/html/b8d18d3d-9db0-43e7-8286-7b46cc3a37ed.htm
> >
> > That seems a comprehensive "root" to a lot of resources -- but if there's
> > a
> > feature chart by Edition, it has eluded me so far.
> >
>
>
Needed software for designing reports
We currently have SQL 2005 (enterprise) reporting services hitting an
odbc based backend (mysql usually). It works great. I run Visual
Studio Pro (and have msdn sql server on my local machine), develop
reports locally and deploy them.
I know the express edition of SQL 2005 reporting services cannot use
an ODBC datasource. Only the standard and up versions.
My question is: For other employees to create and deploy reports what
software (and licenses) are needed? Ideally, I'd love to just deploy
Visual Studio Express and SQL 2005 Express for the users that need to
modify reports, but I have a feeling that won't work...
any ideas?
thank you!If they are just designing reports then you can give the BI Studio (not sure
if that is what it is called). When you install the designer it installs a
version of VS if you do not have it installed. This is free. Also, there are
no licensing issue either. RS is licensed by the server, not by where you
have the client tools installed.
You will want to have a server they can deploy to as part of the development
process, however, for most of their testing they can do this from the
development environment.
If the users can't handle Report Designer (which is really a developer
targeted tool) then check out report builder.
Note, you do not need SQL Server install locally in order to design reports.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<eric.gay@.gmail.com> wrote in message
news:1179174786.894457.142220@.h2g2000hsg.googlegroups.com...
> We currently have SQL 2005 (enterprise) reporting services hitting an
> odbc based backend (mysql usually). It works great. I run Visual
> Studio Pro (and have msdn sql server on my local machine), develop
> reports locally and deploy them.
> I know the express edition of SQL 2005 reporting services cannot use
> an ODBC datasource. Only the standard and up versions.
> My question is: For other employees to create and deploy reports what
> software (and licenses) are needed? Ideally, I'd love to just deploy
> Visual Studio Express and SQL 2005 Express for the users that need to
> modify reports, but I have a feeling that won't work...
> any ideas?
> thank you!
>
odbc based backend (mysql usually). It works great. I run Visual
Studio Pro (and have msdn sql server on my local machine), develop
reports locally and deploy them.
I know the express edition of SQL 2005 reporting services cannot use
an ODBC datasource. Only the standard and up versions.
My question is: For other employees to create and deploy reports what
software (and licenses) are needed? Ideally, I'd love to just deploy
Visual Studio Express and SQL 2005 Express for the users that need to
modify reports, but I have a feeling that won't work...
any ideas?
thank you!If they are just designing reports then you can give the BI Studio (not sure
if that is what it is called). When you install the designer it installs a
version of VS if you do not have it installed. This is free. Also, there are
no licensing issue either. RS is licensed by the server, not by where you
have the client tools installed.
You will want to have a server they can deploy to as part of the development
process, however, for most of their testing they can do this from the
development environment.
If the users can't handle Report Designer (which is really a developer
targeted tool) then check out report builder.
Note, you do not need SQL Server install locally in order to design reports.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<eric.gay@.gmail.com> wrote in message
news:1179174786.894457.142220@.h2g2000hsg.googlegroups.com...
> We currently have SQL 2005 (enterprise) reporting services hitting an
> odbc based backend (mysql usually). It works great. I run Visual
> Studio Pro (and have msdn sql server on my local machine), develop
> reports locally and deploy them.
> I know the express edition of SQL 2005 reporting services cannot use
> an ODBC datasource. Only the standard and up versions.
> My question is: For other employees to create and deploy reports what
> software (and licenses) are needed? Ideally, I'd love to just deploy
> Visual Studio Express and SQL 2005 Express for the users that need to
> modify reports, but I have a feeling that won't work...
> any ideas?
> thank you!
>
Saturday, February 25, 2012
Need urgent help.. for SQL Server reporting services installation..
hi,
I have SQL Server Express edition installed on my PC , but now I need to use SQL Server reporting service, there is SP1 for express edition contains reporting service with express edition. Here..
http://msdn.microsoft.com/vstudio/express/sql/download/
Do I need to download 213 MB SQL Server 2005 Express Edition Toolkit SP1 ?
or there is any other method to use reporting services ?
Thanks
You will have to download the full install again, there is no way of installing the components seperatly. With SQl 2000 there used to be a seperate DL for Reporting Services, but in the 2005 stream they are all included in the one package.
Need urgent help, this is driving me crazy. SSRS 2000
Hi all,
I am trying to build a reportviewer so that I could use reporting services (due to company's security policy).
I am getting a VERY weird error here.
Before I get on ahead, here is the scenario.
I had created a rdl that will give a certain report based on two parameters. At the moment, I didn't assign the parameters to any default values since i don't want the report to start running. These two parameters are run based on stored procedures to get the starting date and an ending date.
I had tried to view this report on Report Manager and it works.
I had set the parameters this way. NOTE: ReportingServer is the disgused name of the reportserver I am using for privacy purposes
Code Snippet
Dim rs As New ReportingServer.ReportingService
rs.Credentials = System.Net.CredentialCache.DefaultCredentials
'Render arguments
Dim results() As Byte
Dim format As String = "HTML4.0"
Dim historyID As String = Nothing
'PDF Rendering extensions don't have any useful DeviceInfo settings
'the toolbar shown below only affects HTML rendering
Dim devInfo As String = "<DeviceInfo><HTMLFragment>True</HTMLFragment><JavaScript>True</JavaScript><Toolbar>True</Toolbar><Parameters>True</Parameters></DeviceInfo>"
Dim credentials() As ReportingServer.DataSourceCredentials = New ReportingServer.DataSourceCredentials() {}
Dim showHideToggle As String = ""
Dim encoding As String = ""
Dim mimeType As String = ""
Dim warnings() As ReportingServer.Warning = New ReportingServer.Warning(0) {}
Dim reportHistoryParameters() As ReportingServer.ParameterValue = New ReportingServer.ParameterValue() {}
Dim streamIDs() As String = Nothing
Dim sh As ReportingServer.SessionHeader = New ReportingServer.SessionHeader
rs.SessionHeaderValue = sh
But when I started building this reportviewer.aspx, it gives me this error on the following line:-
Code Snippet
results = rs.Render(ReportPath, format, historyID, devInfo, Parameters, credentials, _
showHideToggle, encoding, mimeType, reportHistoryParameters, warnings, streamIDs)
with the error
{"This report requires a default or user-defined value for the report parameter 'start_date'. To run or subscribe to this report, you must provide a parameter value. --> This report requires a default or user-defined value for the report parameter 'start_date'. To run or subscribe to this report, you must provide a parameter value. --> This report requires a default or user-defined value for the report parameter 'start_date'. To run or subscribe to this report, you must provide a parameter value."}
this is occuring on the line where it needs to render the report.
As simple as it is, i tried the following:-
NOTE: some variables has been changed to protect some identity.
Code Snippet
Dim ReportRenderer As New RenderSQLReports
Dim Parameters As int.rrd.sqlreporting_test.ParameterValue() = Nothing
ReportRenderer.RenderReport(Parameters, "/Folder/reportname", "pdffilename.pdf")
What I don't get is that i made sure that it doesn't have any default values.
So I went into this scenario and tried teh following:-
Code Snippet
Dim ReportRenderer As New RenderSQLReports
Dim Parameters() As Reportingservices.ParameterValue = New Reportingservices.ParameterValue(1) {}
Parameters(0) = New Reportingservices.ParameterValue
Parameters(0).Label = "start_date"
Parameters(0).Name = "start_date"
Parameters(0).Value = "10/1/1999 12:00:00 AM"
Parameters(1) = New Reportingservices.ParameterValue
Parameters(1).Label = "end_date"
Parameters(1).Name = "end_date"
Parameters(1).Value = "11/1/1999 12:00:00 AM"
ReportRenderer.RenderReport(Parameters, "/Folder/reportname", "pdffilename.pdf")
And this is what happens. It blows up on this line again. with this error.
Code Snippet
results = rs.Render(ReportPath, format, historyID, devInfo, Parameters, credentials, _
showHideToggle, encoding, mimeType, reportHistoryParameters, warnings, streamIDs)
With the errors
{"Default value or value provided for the report parameter 'start_date' is not a valid value. --> Default value or value provided for the report parameter 'start_date' is not a valid value. --> Default value or value provided for the report parameter 'start_date' is not a valid value."}
This is probably occuring because the date I had provided is not found in the list of dates. I really don't want to default a date at the moment, to allow the user to select a date.
So I finally gave it a date...... a valid date.
Code Snippet
Dim ReportRenderer As New RenderSQLReports
Dim Parameters() As Reportingservices.ParameterValue = New Reportingservices.ParameterValue(1) {}
Parameters(0) = New Reportingservices.ParameterValue
Parameters(0).Label = "start_date"
Parameters(0).Name = "start_date"
Parameters(0).Value = "10/1/2004 12:00:00 AM"
Parameters(1) = New Reportingservices.ParameterValue
Parameters(1).Label = "end_date"
Parameters(1).Name = "end_date"
Parameters(1).Value = "11/1/2004 12:00:00 AM"
ReportRenderer.RenderReport(Parameters, "/Folder/reportname", "pdffilename.pdf")
LO and behold, it works BUT . now i get this error in the aspx code.
Runtime error has occured.
Microsoft JScript runtime error: 'Report' is undefined
on this weird line:- (that was generated automatically)
</script><script language="javascript" type="text/javascript" src="?rs:Command=Get&rc:GetImage=8.00.1038.00Report.js">
</script><script language="javascript" type="text/javascript">
<!--
function OnLoadReport()
{
var pageHits = null;
var rep = new Report(1, 16, pageHits, false, docMapIds); <-where error is occuring.
if (parent != self) parent.OnLoadReport(rep);
}
//-->
</script>
It did show the report, but I don't understand why it is still getting an error here. Moreover, I didn't even get the HTMLViewer too even when I had assigned the devinfo....
Really need some help here, as this is quite urgent.... I am at a loss at this, and maybe that there is an option that I am not seeing or something I am missing. please help .
Bernard
-So close yet so far, How cruel are the software bugs-alright ..
I am solving this bit by bit, but the most important is that I want to get the html report with the Toolbar and parameters to show.
So far I am setting up the default values at the moment, and so far it is rendering the report.
How do I show te Toolbar (HtmlVIEwer) and the Parameters section to show on html ?
I Tried the following in the Devinfo
Dim devInfo As String = "<DeviceInfo><Toolbar>True</Toolbar></DeviceInfo>"
And I got the following error in the Aspx code.
Microsoft JScript runtime error: 'Report' is undefined
on this weird line:- (that was generated automatically)
<script language="javascript" type="text/javascript" src="?rs:Command=Get&rc:GetImage=8.00.1038.00Report.js">
</script><script language="javascript" type="text/javascript">
<!--
function OnLoadReport()
{
var pageHits = null;
var rep = new Report(1, 16, pageHits, false, docMapIds); <-where error is occuring.
if (parent != self) parent.OnLoadReport(rep);
}
//-->
</script>
if anybody could tell me what i need to do, that will be really useful and helpful.
Thanks !
Bernard
-So close yet so far, How cruel are the software bugs-
|||
Btong wrote:
alright ..
I am solving this bit by bit, but the most important is that I want to get the html report with the Toolbar and parameters to show.
So far I am setting up the default values at the moment, and so far it is rendering the report.
How do I show te Toolbar (HtmlVIEwer) and the Parameters section to show on html ?
I Tried the following in the Devinfo
Dim devInfo As String = "<DeviceInfo><Toolbar>True</Toolbar></DeviceInfo>"
And I got the following error in the Aspx code.
Microsoft JScript runtime error: 'Report' is undefinedon this weird line:- (that was generated automatically)
<script language="javascript" type="text/javascript" src="?rs:Command=Get&rc:GetImage=8.00.1038.00Report.js">
</script><script language="javascript" type="text/javascript">
<!--
function OnLoadReport()
{
var pageHits = null;
var rep = new Report(1, 16, pageHits, false, docMapIds); <-where error is occuring.
if (parent != self) parent.OnLoadReport(rep);
}
//-->
</script>
if anybody could tell me what i need to do, that will be really useful and helpful.
Thanks !
Bernard
-So close yet so far, How cruel are the software bugs-
Alright Folks.
Got some good news, Managed to build my own HTMLViewer and ReportViewer with some available source code. I am able to set up the HTML for HTMLViewer and ReportViewer. However, in the course of doing so, I came across a very good question.
I had tried to set up the ASMX and use the property "Parameters" and "Toolbar" to set up the HTMLViewer but to no avail.
Setting "<Parameter>True</Parameter>" in the Devinfo string did not make the Parameters section appear in the HTML.
Setting "<Toolbar>True</Toolbar>" in the devinfo string caused a javascript error as described below:-
Microsoft JScript runtime error: 'Report' is undefined
this occured in :-
<script language="javascript" type="text/javascript" src="?rs:Command=Get&rc:GetImage=8.00.1038.00Report.js">
</script><script language="javascript" type="text/javascript">
<!--
function OnLoadReport()
{
var pageHits = null;
var rep = new Report(1, 16, pageHits, false, docMapIds); <-where error is occuring.
if (parent != self) parent.OnLoadReport(rep);
}
//-->
</script>
If I set these parameters to false, My report does generate in html.
I am wondering whether is this a bug? if this is so, is there a hotfix for it ? Or am I missing something crucial at this point ?
Can someone confirm this ? Thanks !
Bernard
-So close yet so far, How cruel are the software bugs-
|||hi All,
Just had a very interesting conversation with one of the SSRS coders/creators and I am very enlightened in this situation.
I had just confirmed the following:-
1) This is not a bug per say. It was never considered that the rendering the report through API will let you set up the PArameters or the toolbar section.
2) the devinfo is really use for the URL access for the reports.
3) If rendering the reports through API, you have to either set almost all properties to False OR set a null in the "<devinfo></devinfo>" in the devinfo string or it won't render. (getting the javascript error as described as above)
4) This devinfo only works if you are on the Report Manager page and won't work if you are trying to view the htmlviewer in another browser.
There are probably a lot of SSRS developers who may wonder "Why go through all the trouble trying to figure this out" OR "so what?"
Well I could see a couple of scenarios here.
1) Clients have full access to Report Manager. (hence the URL access)
2) Developers have to come up with some way to retrieve the parameters, render the report once. (this prevents the clients from accessing the report manager)
Now I could have gone through the second route, but I figured that maybe I could use the HTMLViewer option you would see in the Report Manager without having to expose the URL directly to the clients. (This is due to Company's policy, firewall issues as well as security issues and sensitive data issues).
I didn't want to build a dozen "middlemen" pages just to collect the parameters and then throw it to the rdl via asmx. (waste of time modifying all of them and really unsensible too).
In the end, I managed to build a class that will help in this situation. Not exposing the url directly when a user tries to view the source, and no one has to know where or what the url is, my ReportViewer page prevents that.
I thought that by using the devinfo through ASMX would provide some sort of Report Manager capability without exposing the direct URL.
No one has yet to ask if there is ever a fix that would allow the devinfo string to be utilized via ASMX (it seems that I was the first one to bring this up). So hopefully this may or may not provide some sort of closure to anyone who might be in the same situation as I am.
Thanks for reading this post !
Monday, February 20, 2012
Need to Understand how to Do Simple Pagination
I'm running Reporting Services 2005 and I need a report that basically
shows only 10 lines per page. I'm trying to google around for answers
on this, but they are not straight forward at all!On Feb 21, 11:33 am, "Daedius" <richard.An...@.gmail.com> wrote:
> I'm running Reporting Services 2005 and I need a report that basically
> shows only 10 lines per page. I'm trying to google around for answers
> on this, but they are not straight forward at all!
I know that if you were using columns in your report, you could group
on expression: =Ceiling(RowNumber(Nothing)/10) where 10 is the number
of lines/rows before starting a new column. I would guess that this
could also be used w/report objects as well (i.e., tables, lists,
etc). Hope this helps.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||You can use something like this. in a page break from group,
=Int((RowNumber(Nothing)-1)/25) 25 is the line to display, in your case it
should be 10..
Amarnath
"Daedius" wrote:
> I'm running Reporting Services 2005 and I need a report that basically
> shows only 10 lines per page. I'm trying to google around for answers
> on this, but they are not straight forward at all!
>
shows only 10 lines per page. I'm trying to google around for answers
on this, but they are not straight forward at all!On Feb 21, 11:33 am, "Daedius" <richard.An...@.gmail.com> wrote:
> I'm running Reporting Services 2005 and I need a report that basically
> shows only 10 lines per page. I'm trying to google around for answers
> on this, but they are not straight forward at all!
I know that if you were using columns in your report, you could group
on expression: =Ceiling(RowNumber(Nothing)/10) where 10 is the number
of lines/rows before starting a new column. I would guess that this
could also be used w/report objects as well (i.e., tables, lists,
etc). Hope this helps.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||You can use something like this. in a page break from group,
=Int((RowNumber(Nothing)-1)/25) 25 is the line to display, in your case it
should be 10..
Amarnath
"Daedius" wrote:
> I'm running Reporting Services 2005 and I need a report that basically
> shows only 10 lines per page. I'm trying to google around for answers
> on this, but they are not straight forward at all!
>
Need to transform table data to excel 2003 files
Hi,
Can I use SQL Server Integration Services to generate Excel 2003 spread
sheets based on or database data?
We already have Excel 2003 templates and we need to generate excel 2003 xls
files based on our database table data. What would b the best way to do
that?
Any help would be appreciated,
Max
"Maxwell2006" <alanalan@.newsgroup.nospam> wrote in message
news:O1R9oeXGHHA.3616@.TK2MSFTNGP06.phx.gbl...
> Hi,
> Can I use SQL Server Integration Services to generate Excel 2003 spread
> sheets based on or database data?
> We already have Excel 2003 templates and we need to generate excel 2003
> xls files based on our database table data. What would b the best way to
> do that?
I did something like this once for an Intranet reporting application. The
best solution (easy and performant) that I came up with was to grab the data
using SELECT ... FOR XML and perform an XSL transformation on it. Excel
2003 has a rich set of features in the XML format (though I don't think you
can embed tables and charts in the Excel XML format files).
|||Hello Mike,
To understand the issue better, I'd like to know how you want to use the
2003 template when transform the data from database to spreedsheet. An
example might be more clear.
You shall be able to export data directly to Excel file in SQL Server. In
Management Studio (2005), right click the database->Tasks->Export data,
follow the wizard to select source and select Microsoft Excle as
destination, and select the destination path of excel file.
Also, in SSIS, you could be more flexisble to get the source of the data.
1. You could use the OLEDB or datareader data source, and use select SQL
query to get the data you want.
2. You could use Excel Destination as the data destination and select Excel
file or create new Excel as you want.
3. YOu also be able to select the proper columns for mapping in able object
and use other data folow transformation if necessary.
As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
the data and do transformation by using XSL.
As for as I know, Excel destination does not include configuration to
create new file from xlt template. This might be finished before
transformation by using an Activex scipt task or a Script task. For example
by using Activex script task you may use code like:
Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
sSourceFileName = "temp.xlt"
sTargetFileName = "test.xls"
sTemplatePath = "C:\"
sTargetPath = "C:\"
sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
day(now) - 1 & " " & sTargetFileName
DTSGlobalVariables("sFileName").Value = sTargetFileName
sSourceFileName = sTemplatePath & sSourceFileName
Dim oFSO
Set oFSO = CreateObject("Scripting.FileSystemObject")
oFSO.CopyFile sSourceFileName, sTargetFileName
Set oFSO = Nothing
If you have any update or comments, please feel free to let's know. Thank
you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:32UR4gaGHHA.2304@.TK2MSFTNGHUB02.phx.gbl...
> Hello Mike,
> To understand the issue better, I'd like to know how you want to use the
> 2003 template when transform the data from database to spreedsheet. An
> example might be more clear.
I don't "want to", I already "did". It's been done. Now if you really want
to help me instead of Max, tell me how to embed charts and graphics in Excel
XML format documents.
> You shall be able to export data directly to Excel file in SQL Server. In
> Management Studio (2005), right click the database->Tasks->Export data,
> follow the wizard to select source and select Microsoft Excle as
> destination, and select the destination path of excel file.
> Also, in SSIS, you could be more flexisble to get the source of the data.
> 1. You could use the OLEDB or datareader data source, and use select SQL
> query to get the data you want.
> 2. You could use Excel Destination as the data destination and select
> Excel
> file or create new Excel as you want.
> 3. YOu also be able to select the proper columns for mapping in able
> object
> and use other data folow transformation if necessary.
> As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
> the data and do transformation by using XSL.
> As for as I know, Excel destination does not include configuration to
> create new file from xlt template. This might be finished before
> transformation by using an Activex scipt task or a Script task. For
> example
> by using Activex script task you may use code like:
>
> Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
> sSourceFileName = "temp.xlt"
> sTargetFileName = "test.xls"
> sTemplatePath = "C:\"
> sTargetPath = "C:\"
> sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
> day(now) - 1 & " " & sTargetFileName
> DTSGlobalVariables("sFileName").Value = sTargetFileName
> sSourceFileName = sTemplatePath & sSourceFileName
> Dim oFSO
> Set oFSO = CreateObject("Scripting.FileSystemObject")
> oFSO.CopyFile sSourceFileName, sTargetFileName
> Set oFSO = Nothing
> If you have any update or comments, please feel free to let's know. Thank
> you.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hello Mike,
Sorry for my fault. My reply is for Max insead of you.
The XML Spreadsheet format describes the contents of the workbook by
persisting cell data and formulas, cell formats, worksheet settings, and
workbook settings. Some Excel features cannot be persisted in XML. The
following Excel features cannot be persisted in XML: Charts
OLE Objects
Drawing shapes or AutoShapes
VBA Projects
Group and Outline
Please see the following article for details:
287739XL2002: Error Message: The Following Features from Your Workbook
Will Not Be Saved in the XML Spreadsheet
http://support.microsoft.com/default.aspx?scid=kb;EN-US;287739
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
Can I use SQL Server Integration Services to generate Excel 2003 spread
sheets based on or database data?
We already have Excel 2003 templates and we need to generate excel 2003 xls
files based on our database table data. What would b the best way to do
that?
Any help would be appreciated,
Max
"Maxwell2006" <alanalan@.newsgroup.nospam> wrote in message
news:O1R9oeXGHHA.3616@.TK2MSFTNGP06.phx.gbl...
> Hi,
> Can I use SQL Server Integration Services to generate Excel 2003 spread
> sheets based on or database data?
> We already have Excel 2003 templates and we need to generate excel 2003
> xls files based on our database table data. What would b the best way to
> do that?
I did something like this once for an Intranet reporting application. The
best solution (easy and performant) that I came up with was to grab the data
using SELECT ... FOR XML and perform an XSL transformation on it. Excel
2003 has a rich set of features in the XML format (though I don't think you
can embed tables and charts in the Excel XML format files).
|||Hello Mike,
To understand the issue better, I'd like to know how you want to use the
2003 template when transform the data from database to spreedsheet. An
example might be more clear.
You shall be able to export data directly to Excel file in SQL Server. In
Management Studio (2005), right click the database->Tasks->Export data,
follow the wizard to select source and select Microsoft Excle as
destination, and select the destination path of excel file.
Also, in SSIS, you could be more flexisble to get the source of the data.
1. You could use the OLEDB or datareader data source, and use select SQL
query to get the data you want.
2. You could use Excel Destination as the data destination and select Excel
file or create new Excel as you want.
3. YOu also be able to select the proper columns for mapping in able object
and use other data folow transformation if necessary.
As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
the data and do transformation by using XSL.
As for as I know, Excel destination does not include configuration to
create new file from xlt template. This might be finished before
transformation by using an Activex scipt task or a Script task. For example
by using Activex script task you may use code like:
Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
sSourceFileName = "temp.xlt"
sTargetFileName = "test.xls"
sTemplatePath = "C:\"
sTargetPath = "C:\"
sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
day(now) - 1 & " " & sTargetFileName
DTSGlobalVariables("sFileName").Value = sTargetFileName
sSourceFileName = sTemplatePath & sSourceFileName
Dim oFSO
Set oFSO = CreateObject("Scripting.FileSystemObject")
oFSO.CopyFile sSourceFileName, sTargetFileName
Set oFSO = Nothing
If you have any update or comments, please feel free to let's know. Thank
you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:32UR4gaGHHA.2304@.TK2MSFTNGHUB02.phx.gbl...
> Hello Mike,
> To understand the issue better, I'd like to know how you want to use the
> 2003 template when transform the data from database to spreedsheet. An
> example might be more clear.
I don't "want to", I already "did". It's been done. Now if you really want
to help me instead of Max, tell me how to embed charts and graphics in Excel
XML format documents.
> You shall be able to export data directly to Excel file in SQL Server. In
> Management Studio (2005), right click the database->Tasks->Export data,
> follow the wizard to select source and select Microsoft Excle as
> destination, and select the destination path of excel file.
> Also, in SSIS, you could be more flexisble to get the source of the data.
> 1. You could use the OLEDB or datareader data source, and use select SQL
> query to get the data you want.
> 2. You could use Excel Destination as the data destination and select
> Excel
> file or create new Excel as you want.
> 3. YOu also be able to select the proper columns for mapping in able
> object
> and use other data folow transformation if necessary.
> As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
> the data and do transformation by using XSL.
> As for as I know, Excel destination does not include configuration to
> create new file from xlt template. This might be finished before
> transformation by using an Activex scipt task or a Script task. For
> example
> by using Activex script task you may use code like:
>
> Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
> sSourceFileName = "temp.xlt"
> sTargetFileName = "test.xls"
> sTemplatePath = "C:\"
> sTargetPath = "C:\"
> sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
> day(now) - 1 & " " & sTargetFileName
> DTSGlobalVariables("sFileName").Value = sTargetFileName
> sSourceFileName = sTemplatePath & sSourceFileName
> Dim oFSO
> Set oFSO = CreateObject("Scripting.FileSystemObject")
> oFSO.CopyFile sSourceFileName, sTargetFileName
> Set oFSO = Nothing
> If you have any update or comments, please feel free to let's know. Thank
> you.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||Hello Mike,
Sorry for my fault. My reply is for Max insead of you.
The XML Spreadsheet format describes the contents of the workbook by
persisting cell data and formulas, cell formats, worksheet settings, and
workbook settings. Some Excel features cannot be persisted in XML. The
following Excel features cannot be persisted in XML: Charts
OLE Objects
Drawing shapes or AutoShapes
VBA Projects
Group and Outline
Please see the following article for details:
287739XL2002: Error Message: The Following Features from Your Workbook
Will Not Be Saved in the XML Spreadsheet
http://support.microsoft.com/default.aspx?scid=kb;EN-US;287739
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
Need to transform table data to excel 2003 files
Hi,
Can I use SQL Server Integration Services to generate Excel 2003 spread
sheets based on or database data?
We already have Excel 2003 templates and we need to generate excel 2003 xls
files based on our database table data. What would b the best way to do
that?
Any help would be appreciated,
Max"Maxwell2006" <alanalan@.newsgroup.nospam> wrote in message
news:O1R9oeXGHHA.3616@.TK2MSFTNGP06.phx.gbl...
> Hi,
> Can I use SQL Server Integration Services to generate Excel 2003 spread
> sheets based on or database data?
> We already have Excel 2003 templates and we need to generate excel 2003
> xls files based on our database table data. What would b the best way to
> do that?
I did something like this once for an Intranet reporting application. The
best solution (easy and performant) that I came up with was to grab the data
using SELECT ... FOR XML and perform an XSL transformation on it. Excel
2003 has a rich set of features in the XML format (though I don't think you
can embed tables and charts in the Excel XML format files).|||Hello Mike,
To understand the issue better, I'd like to know how you want to use the
2003 template when transform the data from database to spreedsheet. An
example might be more clear.
You shall be able to export data directly to Excel file in SQL Server. In
Management Studio (2005), right click the database->Tasks->Export data,
follow the wizard to select source and select Microsoft Excle as
destination, and select the destination path of excel file.
Also, in SSIS, you could be more flexisble to get the source of the data.
1. You could use the OLEDB or datareader data source, and use select SQL
query to get the data you want.
2. You could use Excel Destination as the data destination and select Excel
file or create new Excel as you want.
3. YOu also be able to select the proper columns for mapping in able object
and use other data folow transformation if necessary.
As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
the data and do transformation by using XSL.
As for as I know, Excel destination does not include configuration to
create new file from xlt template. This might be finished before
transformation by using an Activex scipt task or a Script task. For example
by using Activex script task you may use code like:
Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
sSourceFileName = "temp.xlt"
sTargetFileName = "test.xls"
sTemplatePath = "C:\"
sTargetPath = "C:\"
sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
day(now) - 1 & " " & sTargetFileName
DTSGlobalVariables("sFileName").Value = sTargetFileName
sSourceFileName = sTemplatePath & sSourceFileName
Dim oFSO
Set oFSO = CreateObject("Scripting.FileSystemObject")
oFSO.CopyFile sSourceFileName, sTargetFileName
Set oFSO = Nothing
If you have any update or comments, please feel free to let's know. Thank
you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:32UR4gaGHHA.2304@.TK2MSFTNGHUB02.phx.gbl...
> Hello Mike,
> To understand the issue better, I'd like to know how you want to use the
> 2003 template when transform the data from database to spreedsheet. An
> example might be more clear.
I don't "want to", I already "did". It's been done. Now if you really want
to help me instead of Max, tell me how to embed charts and graphics in Excel
XML format documents.
> You shall be able to export data directly to Excel file in SQL Server. In
> Management Studio (2005), right click the database->Tasks->Export data,
> follow the wizard to select source and select Microsoft Excle as
> destination, and select the destination path of excel file.
> Also, in SSIS, you could be more flexisble to get the source of the data.
> 1. You could use the OLEDB or datareader data source, and use select SQL
> query to get the data you want.
> 2. You could use Excel Destination as the data destination and select
> Excel
> file or create new Excel as you want.
> 3. YOu also be able to select the proper columns for mapping in able
> object
> and use other data folow transformation if necessary.
> As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
> the data and do transformation by using XSL.
> As for as I know, Excel destination does not include configuration to
> create new file from xlt template. This might be finished before
> transformation by using an Activex scipt task or a Script task. For
> example
> by using Activex script task you may use code like:
>
> Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
> sSourceFileName = "temp.xlt"
> sTargetFileName = "test.xls"
> sTemplatePath = "C:\"
> sTargetPath = "C:\"
> sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
> day(now) - 1 & " " & sTargetFileName
> DTSGlobalVariables("sFileName").Value = sTargetFileName
> sSourceFileName = sTemplatePath & sSourceFileName
> Dim oFSO
> Set oFSO = CreateObject("Scripting.FileSystemObject")
> oFSO.CopyFile sSourceFileName, sTargetFileName
> Set oFSO = Nothing
> If you have any update or comments, please feel free to let's know. Thank
> you.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ========================================
==========
> Get notification to my posts through email? Please refer to
> l]
> ications
> <[url]http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx" target="_blank">http://msdn.microsoft.com/subscript...ps/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscript...rt/default.aspx>.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Mike,
Sorry for my fault. My reply is for Max insead of you.
The XML Spreadsheet format describes the contents of the workbook by
persisting cell data and formulas, cell formats, worksheet settings, and
workbook settings. Some Excel features cannot be persisted in XML. The
following Excel features cannot be persisted in XML: Charts
OLE Objects
Drawing shapes or AutoShapes
VBA Projects
Group and Outline
Please see the following article for details:
287739 XL2002: Error Message: The Following Features from Your Workbook
Will Not Be Saved in the XML Spreadsheet
http://support.microsoft.com/defaul...kb;EN-US;287739
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============
Can I use SQL Server Integration Services to generate Excel 2003 spread
sheets based on or database data?
We already have Excel 2003 templates and we need to generate excel 2003 xls
files based on our database table data. What would b the best way to do
that?
Any help would be appreciated,
Max"Maxwell2006" <alanalan@.newsgroup.nospam> wrote in message
news:O1R9oeXGHHA.3616@.TK2MSFTNGP06.phx.gbl...
> Hi,
> Can I use SQL Server Integration Services to generate Excel 2003 spread
> sheets based on or database data?
> We already have Excel 2003 templates and we need to generate excel 2003
> xls files based on our database table data. What would b the best way to
> do that?
I did something like this once for an Intranet reporting application. The
best solution (easy and performant) that I came up with was to grab the data
using SELECT ... FOR XML and perform an XSL transformation on it. Excel
2003 has a rich set of features in the XML format (though I don't think you
can embed tables and charts in the Excel XML format files).|||Hello Mike,
To understand the issue better, I'd like to know how you want to use the
2003 template when transform the data from database to spreedsheet. An
example might be more clear.
You shall be able to export data directly to Excel file in SQL Server. In
Management Studio (2005), right click the database->Tasks->Export data,
follow the wizard to select source and select Microsoft Excle as
destination, and select the destination path of excel file.
Also, in SSIS, you could be more flexisble to get the source of the data.
1. You could use the OLEDB or datareader data source, and use select SQL
query to get the data you want.
2. You could use Excel Destination as the data destination and select Excel
file or create new Excel as you want.
3. YOu also be able to select the proper columns for mapping in able object
and use other data folow transformation if necessary.
As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
the data and do transformation by using XSL.
As for as I know, Excel destination does not include configuration to
create new file from xlt template. This might be finished before
transformation by using an Activex scipt task or a Script task. For example
by using Activex script task you may use code like:
Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
sSourceFileName = "temp.xlt"
sTargetFileName = "test.xls"
sTemplatePath = "C:\"
sTargetPath = "C:\"
sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
day(now) - 1 & " " & sTargetFileName
DTSGlobalVariables("sFileName").Value = sTargetFileName
sSourceFileName = sTemplatePath & sSourceFileName
Dim oFSO
Set oFSO = CreateObject("Scripting.FileSystemObject")
oFSO.CopyFile sSourceFileName, sTargetFileName
Set oFSO = Nothing
If you have any update or comments, please feel free to let's know. Thank
you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
========================================
==========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
<http://msdn.microsoft.com/subscript...ps/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscript...rt/default.aspx>.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:32UR4gaGHHA.2304@.TK2MSFTNGHUB02.phx.gbl...
> Hello Mike,
> To understand the issue better, I'd like to know how you want to use the
> 2003 template when transform the data from database to spreedsheet. An
> example might be more clear.
I don't "want to", I already "did". It's been done. Now if you really want
to help me instead of Max, tell me how to embed charts and graphics in Excel
XML format documents.
> You shall be able to export data directly to Excel file in SQL Server. In
> Management Studio (2005), right click the database->Tasks->Export data,
> follow the wizard to select source and select Microsoft Excle as
> destination, and select the destination path of excel file.
> Also, in SSIS, you could be more flexisble to get the source of the data.
> 1. You could use the OLEDB or datareader data source, and use select SQL
> query to get the data you want.
> 2. You could use Excel Destination as the data destination and select
> Excel
> file or create new Excel as you want.
> 3. YOu also be able to select the proper columns for mapping in able
> object
> and use other data folow transformation if necessary.
> As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
> the data and do transformation by using XSL.
> As for as I know, Excel destination does not include configuration to
> create new file from xlt template. This might be finished before
> transformation by using an Activex scipt task or a Script task. For
> example
> by using Activex script task you may use code like:
>
> Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
> sSourceFileName = "temp.xlt"
> sTargetFileName = "test.xls"
> sTemplatePath = "C:\"
> sTargetPath = "C:\"
> sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
> day(now) - 1 & " " & sTargetFileName
> DTSGlobalVariables("sFileName").Value = sTargetFileName
> sSourceFileName = sTemplatePath & sSourceFileName
> Dim oFSO
> Set oFSO = CreateObject("Scripting.FileSystemObject")
> oFSO.CopyFile sSourceFileName, sTargetFileName
> Set oFSO = Nothing
> If you have any update or comments, please feel free to let's know. Thank
> you.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ========================================
==========
> Get notification to my posts through email? Please refer to
> l]
> ications
> <[url]http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx" target="_blank">http://msdn.microsoft.com/subscript...ps/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscript...rt/default.aspx>.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Mike,
Sorry for my fault. My reply is for Max insead of you.
The XML Spreadsheet format describes the contents of the workbook by
persisting cell data and formulas, cell formats, worksheet settings, and
workbook settings. Some Excel features cannot be persisted in XML. The
following Excel features cannot be persisted in XML: Charts
OLE Objects
Drawing shapes or AutoShapes
VBA Projects
Group and Outline
Please see the following article for details:
287739 XL2002: Error Message: The Following Features from Your Workbook
Will Not Be Saved in the XML Spreadsheet
http://support.microsoft.com/defaul...kb;EN-US;287739
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============
Need to transform table data to excel 2003 files
Hi,
Can I use SQL Server Integration Services to generate Excel 2003 spread
sheets based on or database data?
We already have Excel 2003 templates and we need to generate excel 2003 xls
files based on our database table data. What would b the best way to do
that?
Any help would be appreciated,
Max"Maxwell2006" <alanalan@.newsgroup.nospam> wrote in message
news:O1R9oeXGHHA.3616@.TK2MSFTNGP06.phx.gbl...
> Hi,
> Can I use SQL Server Integration Services to generate Excel 2003 spread
> sheets based on or database data?
> We already have Excel 2003 templates and we need to generate excel 2003
> xls files based on our database table data. What would b the best way to
> do that?
I did something like this once for an Intranet reporting application. The
best solution (easy and performant) that I came up with was to grab the data
using SELECT ... FOR XML and perform an XSL transformation on it. Excel
2003 has a rich set of features in the XML format (though I don't think you
can embed tables and charts in the Excel XML format files).|||Hello Mike,
To understand the issue better, I'd like to know how you want to use the
2003 template when transform the data from database to spreedsheet. An
example might be more clear.
You shall be able to export data directly to Excel file in SQL Server. In
Management Studio (2005), right click the database->Tasks->Export data,
follow the wizard to select source and select Microsoft Excle as
destination, and select the destination path of excel file.
Also, in SSIS, you could be more flexisble to get the source of the data.
1. You could use the OLEDB or datareader data source, and use select SQL
query to get the data you want.
2. You could use Excel Destination as the data destination and select Excel
file or create new Excel as you want.
3. YOu also be able to select the proper columns for mapping in able object
and use other data folow transformation if necessary.
As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
the data and do transformation by using XSL.
As for as I know, Excel destination does not include configuration to
create new file from xlt template. This might be finished before
transformation by using an Activex scipt task or a Script task. For example
by using Activex script task you may use code like:
Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
sSourceFileName = "temp.xlt"
sTargetFileName = "test.xls"
sTemplatePath = "C:\"
sTargetPath = "C:\"
sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
day(now) - 1 & " " & sTargetFileName
DTSGlobalVariables("sFileName").Value = sTargetFileName
sSourceFileName = sTemplatePath & sSourceFileName
Dim oFSO
Set oFSO = CreateObject("Scripting.FileSystemObject")
oFSO.CopyFile sSourceFileName, sTargetFileName
Set oFSO = Nothing
If you have any update or comments, please feel free to let's know. Thank
you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:32UR4gaGHHA.2304@.TK2MSFTNGHUB02.phx.gbl...
> Hello Mike,
> To understand the issue better, I'd like to know how you want to use the
> 2003 template when transform the data from database to spreedsheet. An
> example might be more clear.
I don't "want to", I already "did". It's been done. Now if you really want
to help me instead of Max, tell me how to embed charts and graphics in Excel
XML format documents.
> You shall be able to export data directly to Excel file in SQL Server. In
> Management Studio (2005), right click the database->Tasks->Export data,
> follow the wizard to select source and select Microsoft Excle as
> destination, and select the destination path of excel file.
> Also, in SSIS, you could be more flexisble to get the source of the data.
> 1. You could use the OLEDB or datareader data source, and use select SQL
> query to get the data you want.
> 2. You could use Excel Destination as the data destination and select
> Excel
> file or create new Excel as you want.
> 3. YOu also be able to select the proper columns for mapping in able
> object
> and use other data folow transformation if necessary.
> As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
> the data and do transformation by using XSL.
> As for as I know, Excel destination does not include configuration to
> create new file from xlt template. This might be finished before
> transformation by using an Activex scipt task or a Script task. For
> example
> by using Activex script task you may use code like:
>
> Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
> sSourceFileName = "temp.xlt"
> sTargetFileName = "test.xls"
> sTemplatePath = "C:\"
> sTargetPath = "C:\"
> sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
> day(now) - 1 & " " & sTargetFileName
> DTSGlobalVariables("sFileName").Value = sTargetFileName
> sSourceFileName = sTemplatePath & sSourceFileName
> Dim oFSO
> Set oFSO = CreateObject("Scripting.FileSystemObject")
> oFSO.CopyFile sSourceFileName, sTargetFileName
> Set oFSO = Nothing
> If you have any update or comments, please feel free to let's know. Thank
> you.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Mike,
Sorry for my fault. My reply is for Max insead of you.
The XML Spreadsheet format describes the contents of the workbook by
persisting cell data and formulas, cell formats, worksheet settings, and
workbook settings. Some Excel features cannot be persisted in XML. The
following Excel features cannot be persisted in XML: ? Charts
? OLE Objects
? Drawing shapes or AutoShapes
? VBA Projects
? Group and Outline
Please see the following article for details:
287739 XL2002: Error Message: The Following Features from Your Workbook
Will Not Be Saved in the XML Spreadsheet
http://support.microsoft.com/default.aspx?scid=kb;EN-US;287739
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
Can I use SQL Server Integration Services to generate Excel 2003 spread
sheets based on or database data?
We already have Excel 2003 templates and we need to generate excel 2003 xls
files based on our database table data. What would b the best way to do
that?
Any help would be appreciated,
Max"Maxwell2006" <alanalan@.newsgroup.nospam> wrote in message
news:O1R9oeXGHHA.3616@.TK2MSFTNGP06.phx.gbl...
> Hi,
> Can I use SQL Server Integration Services to generate Excel 2003 spread
> sheets based on or database data?
> We already have Excel 2003 templates and we need to generate excel 2003
> xls files based on our database table data. What would b the best way to
> do that?
I did something like this once for an Intranet reporting application. The
best solution (easy and performant) that I came up with was to grab the data
using SELECT ... FOR XML and perform an XSL transformation on it. Excel
2003 has a rich set of features in the XML format (though I don't think you
can embed tables and charts in the Excel XML format files).|||Hello Mike,
To understand the issue better, I'd like to know how you want to use the
2003 template when transform the data from database to spreedsheet. An
example might be more clear.
You shall be able to export data directly to Excel file in SQL Server. In
Management Studio (2005), right click the database->Tasks->Export data,
follow the wizard to select source and select Microsoft Excle as
destination, and select the destination path of excel file.
Also, in SSIS, you could be more flexisble to get the source of the data.
1. You could use the OLEDB or datareader data source, and use select SQL
query to get the data you want.
2. You could use Excel Destination as the data destination and select Excel
file or create new Excel as you want.
3. YOu also be able to select the proper columns for mapping in able object
and use other data folow transformation if necessary.
As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
the data and do transformation by using XSL.
As for as I know, Excel destination does not include configuration to
create new file from xlt template. This might be finished before
transformation by using an Activex scipt task or a Script task. For example
by using Activex script task you may use code like:
Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
sSourceFileName = "temp.xlt"
sTargetFileName = "test.xls"
sTemplatePath = "C:\"
sTargetPath = "C:\"
sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
day(now) - 1 & " " & sTargetFileName
DTSGlobalVariables("sFileName").Value = sTargetFileName
sSourceFileName = sTemplatePath & sSourceFileName
Dim oFSO
Set oFSO = CreateObject("Scripting.FileSystemObject")
oFSO.CopyFile sSourceFileName, sTargetFileName
Set oFSO = Nothing
If you have any update or comments, please feel free to let's know. Thank
you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||"Peter Yang [MSFT]" <petery@.online.microsoft.com> wrote in message
news:32UR4gaGHHA.2304@.TK2MSFTNGHUB02.phx.gbl...
> Hello Mike,
> To understand the issue better, I'd like to know how you want to use the
> 2003 template when transform the data from database to spreedsheet. An
> example might be more clear.
I don't "want to", I already "did". It's been done. Now if you really want
to help me instead of Max, tell me how to embed charts and graphics in Excel
XML format documents.
> You shall be able to export data directly to Excel file in SQL Server. In
> Management Studio (2005), right click the database->Tasks->Export data,
> follow the wizard to select source and select Microsoft Excle as
> destination, and select the destination path of excel file.
> Also, in SSIS, you could be more flexisble to get the source of the data.
> 1. You could use the OLEDB or datareader data source, and use select SQL
> query to get the data you want.
> 2. You could use Excel Destination as the data destination and select
> Excel
> file or create new Excel as you want.
> 3. YOu also be able to select the proper columns for mapping in able
> object
> and use other data folow transformation if necessary.
> As Mike mentioned, you could use "SELECT ... FOR XML" to get XML format of
> the data and do transformation by using XSL.
> As for as I know, Excel destination does not include configuration to
> create new file from xlt template. This might be finished before
> transformation by using an Activex scipt task or a Script task. For
> example
> by using Activex script task you may use code like:
>
> Dim sTemplatePath, sTargetPath, sSourceFileName, sTargetFileName
> sSourceFileName = "temp.xlt"
> sTargetFileName = "test.xls"
> sTemplatePath = "C:\"
> sTargetPath = "C:\"
> sTargetFileName = sTargetPath & year(now) & "-" & month(now) & "-" &
> day(now) - 1 & " " & sTargetFileName
> DTSGlobalVariables("sFileName").Value = sTargetFileName
> sSourceFileName = sTemplatePath & sSourceFileName
> Dim oFSO
> Set oFSO = CreateObject("Scripting.FileSystemObject")
> oFSO.CopyFile sSourceFileName, sTargetFileName
> Set oFSO = Nothing
> If you have any update or comments, please feel free to let's know. Thank
> you.
> Best Regards,
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications
> <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> <http://msdn.microsoft.com/subscriptions/support/default.aspx>.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hello Mike,
Sorry for my fault. My reply is for Max insead of you.
The XML Spreadsheet format describes the contents of the workbook by
persisting cell data and formulas, cell formats, worksheet settings, and
workbook settings. Some Excel features cannot be persisted in XML. The
following Excel features cannot be persisted in XML: ? Charts
? OLE Objects
? Drawing shapes or AutoShapes
? VBA Projects
? Group and Outline
Please see the following article for details:
287739 XL2002: Error Message: The Following Features from Your Workbook
Will Not Be Saved in the XML Spreadsheet
http://support.microsoft.com/default.aspx?scid=kb;EN-US;287739
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
Need to suppress repeating values in parameter drop-down list
I'm using a Report Parameter within a SQL Reporting Services Report, and the appropriate values are populating the parameter drop-down list. However, one of my tables has several records with the Service Provider ID. My question is how can repeating values be suppressed in the parameter drop-down list. See below for example. Any insight/advice is appreciated!
Service Provider ID 21
50
60
60
60
you can do a SELECT DISTINCT in your query to get unique records.
Service Provider ID 21
50
60
60
60
you can do a SELECT DISTINCT in your query to get unique records.
Subscribe to:
Posts (Atom)