Main report drive Subreports

Will SRS support passing parameters from the main report to the subreport
which calls a stored proc that does not contain any parameters ? it will
automatically filter the data without the where clause.
I used to be able to do this in Crystal reports which I don't need to
specify a where clause in my subreport stored proc and I am not sure if SRS
will support this and I hope that I don't need to rewrite all the stored proc
for this.
Need help on this one !
ThanksRS has two different ways of filtering the data. One is to use it as a query
filter. In this case the parameter would either part of the query or passed
to a stored procedure. SQL Server would then only return the necessary data
to the report. The other possibility is to use a filter. The filter has RS
filter the data. Whatever data is defined in the dataset goes to the report
and then the report filters the data. I stay away from this because it is
much more efficient for the database to send only the necessary records to
Reporting Services. However, it sound like you want to use filters.
You would do the following. Create a subreport with a parameter. Use the
parameter in your filter. When you embed the subreport into the report then
do a right mouse click on the subreport and map the report parameter to
whatever is appropriate on the main report.
So in your case the subreport has a dataset based on a stored procedure that
has no parameters. That dataset returns the data. Then using the report
parameter passed into it by the main report, the report takes the data from
the stored procedure and filters it.
Read up in book online on filtering. You can apply the filter in multiple
spots. The value you want to filter on would be an expression which is where
you would then reference the report parameter.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Eric Hu" <EricHu@.discussions.microsoft.com> wrote in message
news:132A8634-04DA-4688-8C40-F53513085D43@.microsoft.com...
> Will SRS support passing parameters from the main report to the subreport
> which calls a stored proc that does not contain any parameters ? it will
> automatically filter the data without the where clause.
> I used to be able to do this in Crystal reports which I don't need to
> specify a where clause in my subreport stored proc and I am not sure if
> SRS
> will support this and I hope that I don't need to rewrite all the stored
> proc
> for this.
> Need help on this one !
> Thanks|||Brian,
In my report parameter, it's either a single area or all areas. The filter
works good with one area, but when I select all areas I want to have all
recordset coming back. Is there a way to conditionally turn the filter on or
off ? I only need to filter if the user select a single area.
Thanks,
Eric
"Bruce L-C [MVP]" wrote:
> RS has two different ways of filtering the data. One is to use it as a query
> filter. In this case the parameter would either part of the query or passed
> to a stored procedure. SQL Server would then only return the necessary data
> to the report. The other possibility is to use a filter. The filter has RS
> filter the data. Whatever data is defined in the dataset goes to the report
> and then the report filters the data. I stay away from this because it is
> much more efficient for the database to send only the necessary records to
> Reporting Services. However, it sound like you want to use filters.
> You would do the following. Create a subreport with a parameter. Use the
> parameter in your filter. When you embed the subreport into the report then
> do a right mouse click on the subreport and map the report parameter to
> whatever is appropriate on the main report.
> So in your case the subreport has a dataset based on a stored procedure that
> has no parameters. That dataset returns the data. Then using the report
> parameter passed into it by the main report, the report takes the data from
> the stored procedure and filters it.
> Read up in book online on filtering. You can apply the filter in multiple
> spots. The value you want to filter on would be an expression which is where
> you would then reference the report parameter.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Eric Hu" <EricHu@.discussions.microsoft.com> wrote in message
> news:132A8634-04DA-4688-8C40-F53513085D43@.microsoft.com...
> > Will SRS support passing parameters from the main report to the subreport
> > which calls a stored proc that does not contain any parameters ? it will
> > automatically filter the data without the where clause.
> >
> > I used to be able to do this in Crystal reports which I don't need to
> > specify a where clause in my subreport stored proc and I am not sure if
> > SRS
> > will support this and I hope that I don't need to rewrite all the stored
> > proc
> > for this.
> >
> > Need help on this one !
> >
> > Thanks
>
>|||The filter is an expression. You should be able to do this.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Eric Hu" <EricHu@.discussions.microsoft.com> wrote in message
news:00C86BEC-B4EC-4A91-8E09-D4C549915CD7@.microsoft.com...
> Brian,
> In my report parameter, it's either a single area or all areas. The filter
> works good with one area, but when I select all areas I want to have all
> recordset coming back. Is there a way to conditionally turn the filter on
> or
> off ? I only need to filter if the user select a single area.
> Thanks,
> Eric
> "Bruce L-C [MVP]" wrote:
>> RS has two different ways of filtering the data. One is to use it as a
>> query
>> filter. In this case the parameter would either part of the query or
>> passed
>> to a stored procedure. SQL Server would then only return the necessary
>> data
>> to the report. The other possibility is to use a filter. The filter has
>> RS
>> filter the data. Whatever data is defined in the dataset goes to the
>> report
>> and then the report filters the data. I stay away from this because it is
>> much more efficient for the database to send only the necessary records
>> to
>> Reporting Services. However, it sound like you want to use filters.
>> You would do the following. Create a subreport with a parameter. Use the
>> parameter in your filter. When you embed the subreport into the report
>> then
>> do a right mouse click on the subreport and map the report parameter to
>> whatever is appropriate on the main report.
>> So in your case the subreport has a dataset based on a stored procedure
>> that
>> has no parameters. That dataset returns the data. Then using the report
>> parameter passed into it by the main report, the report takes the data
>> from
>> the stored procedure and filters it.
>> Read up in book online on filtering. You can apply the filter in multiple
>> spots. The value you want to filter on would be an expression which is
>> where
>> you would then reference the report parameter.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Eric Hu" <EricHu@.discussions.microsoft.com> wrote in message
>> news:132A8634-04DA-4688-8C40-F53513085D43@.microsoft.com...
>> > Will SRS support passing parameters from the main report to the
>> > subreport
>> > which calls a stored proc that does not contain any parameters ? it
>> > will
>> > automatically filter the data without the where clause.
>> >
>> > I used to be able to do this in Crystal reports which I don't need to
>> > specify a where clause in my subreport stored proc and I am not sure if
>> > SRS
>> > will support this and I hope that I don't need to rewrite all the
>> > stored
>> > proc
>> > for this.
>> >
>> > Need help on this one !
>> >
>> > Thanks
>>|||Thanks for the quick reply. I am not sure how to do this.
The way the filter works is that:
In Expression, type or select the expression for the field that you want the
filter to evaluate.
In Operator, select the operator that you want the filter to use to compare
the evaluated field and the value.
In Value, type the expression or value against which you want the filter to
evaluate the value in Expression.
Seem like you always need to assign a value to a filter, so in the case of
all values , I don't want to have a filter and how will this work with
expression ?
"Bruce L-C [MVP]" wrote:
> The filter is an expression. You should be able to do this.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Eric Hu" <EricHu@.discussions.microsoft.com> wrote in message
> news:00C86BEC-B4EC-4A91-8E09-D4C549915CD7@.microsoft.com...
> > Brian,
> >
> > In my report parameter, it's either a single area or all areas. The filter
> > works good with one area, but when I select all areas I want to have all
> > recordset coming back. Is there a way to conditionally turn the filter on
> > or
> > off ? I only need to filter if the user select a single area.
> >
> > Thanks,
> > Eric
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> RS has two different ways of filtering the data. One is to use it as a
> >> query
> >> filter. In this case the parameter would either part of the query or
> >> passed
> >> to a stored procedure. SQL Server would then only return the necessary
> >> data
> >> to the report. The other possibility is to use a filter. The filter has
> >> RS
> >> filter the data. Whatever data is defined in the dataset goes to the
> >> report
> >> and then the report filters the data. I stay away from this because it is
> >> much more efficient for the database to send only the necessary records
> >> to
> >> Reporting Services. However, it sound like you want to use filters.
> >>
> >> You would do the following. Create a subreport with a parameter. Use the
> >> parameter in your filter. When you embed the subreport into the report
> >> then
> >> do a right mouse click on the subreport and map the report parameter to
> >> whatever is appropriate on the main report.
> >>
> >> So in your case the subreport has a dataset based on a stored procedure
> >> that
> >> has no parameters. That dataset returns the data. Then using the report
> >> parameter passed into it by the main report, the report takes the data
> >> from
> >> the stored procedure and filters it.
> >>
> >> Read up in book online on filtering. You can apply the filter in multiple
> >> spots. The value you want to filter on would be an expression which is
> >> where
> >> you would then reference the report parameter.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Eric Hu" <EricHu@.discussions.microsoft.com> wrote in message
> >> news:132A8634-04DA-4688-8C40-F53513085D43@.microsoft.com...
> >> > Will SRS support passing parameters from the main report to the
> >> > subreport
> >> > which calls a stored proc that does not contain any parameters ? it
> >> > will
> >> > automatically filter the data without the where clause.
> >> >
> >> > I used to be able to do this in Crystal reports which I don't need to
> >> > specify a where clause in my subreport stored proc and I am not sure if
> >> > SRS
> >> > will support this and I hope that I don't need to rewrite all the
> >> > stored
> >> > proc
> >> > for this.
> >> >
> >> > Need help on this one !
> >> >
> >> > Thanks
> >>
> >>
> >>
>
>

Main report Calls subreport Sps when subreport is set to invisible.

Hello,
I have about 15 subreports in main report, and i am making then visible/invisible based on the selection criteria. Currently even i make a subreport invisible, then also i found using profiler that it is calling SP. so the performance doesnot gets improved !

I want to stop these calls when the subreport is invisible! that helps me a gr8!
OR -
Is there any setting in the config file to avoid this ?

please reply ASAP.

Thanks in advance,
Abhay Lakkad

Currently, subreports will still get executed if the end up being invisible in the main report. We will improve this in future releases.

-- Robert

|||

Just wondered if there is any kind of work-around for this, or if it will be addressed in an upcoming RS 2005 service pack.

Thanks
Marie

Main report Calls subreport Sps when subreport is set to invisible.

Hello,
I have about 15 subreports in main report, and i am making then visible/invisible based on the selection criteria. Currently even i make a subreport invisible, then also i found using profiler that it is calling SP. so the performance doesnot gets improved !

I want to stop these calls when the subreport is invisible! that helps me a gr8!
OR -
Is there any setting in the config file to avoid this ?

please reply ASAP.

Thanks in advance,
Abhay Lakkad

Currently, subreports will still get executed if the end up being invisible in the main report. We will improve this in future releases.

-- Robert

|||

Just wondered if there is any kind of work-around for this, or if it will be addressed in an upcoming RS 2005 service pack.

Thanks
Marie

mailto and picking a field for the subject line

I've put a hyperlink on a report to send a message to the support center
concerning service calls that are overdue for closure. How can I assign one
of the report fields as the subject of the mail message? For instance, if
the user clicks the 'Send Mail' link, the subject of the mail is "Call Number
"& "Field.svc00200.
Mail system is Exchange.
Many thanks
(BTW--I know 0 .net code, so keep that in mind, lol)Build the url string programmatically. I know you say you don't know
.Net but in RS a little knowledge goes a long way!
Where you would type the url, try
="mailto:" + Fields!email.Value + "&Subject=Call number" +
Fields!svc00200.Value
Chris
Jeff Metcalf wrote:
> I've put a hyperlink on a report to send a message to the support
> center concerning service calls that are overdue for closure. How
> can I assign one of the report fields as the subject of the mail
> message? For instance, if the user clicks the 'Send Mail' link, the
> subject of the mail is "Call Number "& "Field.svc00200.
> Mail system is Exchange.
> Many thanks
> (BTW--I know 0 .net code, so keep that in mind, lol)|||Nope, doesn't work. Gets Invalid URI: The hostname could not be parsed.
="Mailto:dispatch@.blah.com"+"&Subject=Call Number
"+Fields!svc00200.callnbr.Value
"Chris McGuigan" wrote:
> Build the url string programmatically. I know you say you don't know
> ..Net but in RS a little knowledge goes a long way!
> Where you would type the url, try
> ="mailto:" + Fields!email.Value + "&Subject=Call number" +
> Fields!svc00200.Value
> Chris
>
> Jeff Metcalf wrote:
> > I've put a hyperlink on a report to send a message to the support
> > center concerning service calls that are overdue for closure. How
> > can I assign one of the report fields as the subject of the mail
> > message? For instance, if the user clicks the 'Send Mail' link, the
> > subject of the mail is "Call Number "& "Field.svc00200.
> >
> > Mail system is Exchange.
> >
> > Many thanks
> > (BTW--I know 0 .net code, so keep that in mind, lol)
>|||I'm guessing it's a typo, but you have Fields!svc00200.callnbr.Value,
that doesn't look valid to me!
I have had this working, so it is possible. You probably haven't quite
got the expression right. Are there any characters in the returned
field that would effect the parsing, eg &
Chris
Jeff Metcalf wrote:
> Nope, doesn't work. Gets Invalid URI: The hostname could not be
> parsed.
> ="Mailto:dispatch@.blah.com"+"&Subject=Call Number
> "+Fields!svc00200.callnbr.Value
> "Chris McGuigan" wrote:
> > Build the url string programmatically. I know you say you don't know
> > ..Net but in RS a little knowledge goes a long way!
> > Where you would type the url, try
> > ="mailto:" + Fields!email.Value + "&Subject=Call number" +
> > Fields!svc00200.Value
> >
> > Chris
> >
> >
> > Jeff Metcalf wrote:
> >
> > > I've put a hyperlink on a report to send a message to the support
> > > center concerning service calls that are overdue for closure. How
> > > can I assign one of the report fields as the subject of the mail
> > > message? For instance, if the user clicks the 'Send Mail' link,
> > > the subject of the mail is "Call Number "& "Field.svc00200.
> > >
> > > Mail system is Exchange.
> > >
> > > Many thanks
> > > (BTW--I know 0 .net code, so keep that in mind, lol)
> >
> >

Macintosh Excel v.x Rendering

We have built a new front end to the report server to run reports. When
making calls to the RS Web Service, is there anything special that needs to
be done for Excel (xls) rendering? We have a few clients utlizing Apple MAC
OS X with Office v.x. We thought that SP1 would take care of their ability
to open the xls files as with prior versions of PC xls before Office XP.
After further testing, the MAC version still does not open the excel file
correctly. It only has MIME type values in the file. What are the options
to ensure MAC Excel opens the same as PC Excel with SP1? We currently have
them export to CSV and then open that in excel with the text to columns
re-formatting. Any help you could provide would be greatly appreciated.Have you tried to export the file using a PC, save it to disk and then open
it on the Mac? I wouldn't be surprised if there were some glitches.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lance" <Lance@.discussions.microsoft.com> wrote in message
news:061952A6-F39C-49F3-AA13-F568C4588772@.microsoft.com...
> We have built a new front end to the report server to run reports. When
> making calls to the RS Web Service, is there anything special that needs
> to
> be done for Excel (xls) rendering? We have a few clients utlizing Apple
> MAC
> OS X with Office v.x. We thought that SP1 would take care of their
> ability
> to open the xls files as with prior versions of PC xls before Office XP.
> After further testing, the MAC version still does not open the excel file
> correctly. It only has MIME type values in the file. What are the
> options
> to ensure MAC Excel opens the same as PC Excel with SP1? We currently
> have
> them export to CSV and then open that in excel with the text to columns
> re-formatting. Any help you could provide would be greatly appreciated.|||Yes...It works fine if I save down to Excel 95-2000 workbook and then send
it. The mac opens fine, but that is not a viable solution to our problem as
the mac clients will need to run reports on demand. Do you by chance know
if there is a solution in the works to ensure MAC Excel versions export
without incidence as the PC version?
Thanks...
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:Ohc$PCnfEHA.2764@.TK2MSFTNGP11.phx.gbl...
> Have you tried to export the file using a PC, save it to disk and then
open
> it on the Mac? I wouldn't be surprised if there were some glitches.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Lance" <Lance@.discussions.microsoft.com> wrote in message
> news:061952A6-F39C-49F3-AA13-F568C4588772@.microsoft.com...
> > We have built a new front end to the report server to run reports. When
> > making calls to the RS Web Service, is there anything special that needs
> > to
> > be done for Excel (xls) rendering? We have a few clients utlizing Apple
> > MAC
> > OS X with Office v.x. We thought that SP1 would take care of their
> > ability
> > to open the xls files as with prior versions of PC xls before Office XP.
> > After further testing, the MAC version still does not open the excel
file
> > correctly. It only has MIME type values in the file. What are the
> > options
> > to ensure MAC Excel opens the same as PC Excel with SP1? We currently
> > have
> > them export to CSV and then open that in excel with the text to columns
> > re-formatting. Any help you could provide would be greatly appreciated.
>|||So what happens if you open the workbook directly in Excel on the mac (don't
open it in PC Excel)?
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lance" <ldacy@.fellowshiptech.com> wrote in message
news:ueFapmtfEHA.2848@.TK2MSFTNGP10.phx.gbl...
> Yes...It works fine if I save down to Excel 95-2000 workbook and then send
> it. The mac opens fine, but that is not a viable solution to our problem
> as
> the mac clients will need to run reports on demand. Do you by chance know
> if there is a solution in the works to ensure MAC Excel versions export
> without incidence as the PC version?
> Thanks...
> "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> news:Ohc$PCnfEHA.2764@.TK2MSFTNGP11.phx.gbl...
>> Have you tried to export the file using a PC, save it to disk and then
> open
>> it on the Mac? I wouldn't be surprised if there were some glitches.
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> "Lance" <Lance@.discussions.microsoft.com> wrote in message
>> news:061952A6-F39C-49F3-AA13-F568C4588772@.microsoft.com...
>> > We have built a new front end to the report server to run reports.
>> > When
>> > making calls to the RS Web Service, is there anything special that
>> > needs
>> > to
>> > be done for Excel (xls) rendering? We have a few clients utlizing
>> > Apple
>> > MAC
>> > OS X with Office v.x. We thought that SP1 would take care of their
>> > ability
>> > to open the xls files as with prior versions of PC xls before Office
>> > XP.
>> > After further testing, the MAC version still does not open the excel
> file
>> > correctly. It only has MIME type values in the file. What are the
>> > options
>> > to ensure MAC Excel opens the same as PC Excel with SP1? We currently
>> > have
>> > them export to CSV and then open that in excel with the text to columns
>> > re-formatting. Any help you could provide would be greatly
>> > appreciated.
>>
>|||The document is garbage...It looks exactly what happens when someone who has
a lower version of excel than XP.
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:enJe9r8fEHA.536@.TK2MSFTNGP11.phx.gbl...
> So what happens if you open the workbook directly in Excel on the mac
(don't
> open it in PC Excel)?
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Lance" <ldacy@.fellowshiptech.com> wrote in message
> news:ueFapmtfEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > Yes...It works fine if I save down to Excel 95-2000 workbook and then
send
> > it. The mac opens fine, but that is not a viable solution to our
problem
> > as
> > the mac clients will need to run reports on demand. Do you by chance
know
> > if there is a solution in the works to ensure MAC Excel versions export
> > without incidence as the PC version?
> >
> > Thanks...
> >
> > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> > news:Ohc$PCnfEHA.2764@.TK2MSFTNGP11.phx.gbl...
> >> Have you tried to export the file using a PC, save it to disk and then
> > open
> >> it on the Mac? I wouldn't be surprised if there were some glitches.
> >>
> >> --
> >> Brian Welcker
> >> Group Program Manager
> >> Microsoft SQL Server Reporting Services
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >> "Lance" <Lance@.discussions.microsoft.com> wrote in message
> >> news:061952A6-F39C-49F3-AA13-F568C4588772@.microsoft.com...
> >> > We have built a new front end to the report server to run reports.
> >> > When
> >> > making calls to the RS Web Service, is there anything special that
> >> > needs
> >> > to
> >> > be done for Excel (xls) rendering? We have a few clients utlizing
> >> > Apple
> >> > MAC
> >> > OS X with Office v.x. We thought that SP1 would take care of their
> >> > ability
> >> > to open the xls files as with prior versions of PC xls before Office
> >> > XP.
> >> > After further testing, the MAC version still does not open the excel
> > file
> >> > correctly. It only has MIME type values in the file. What are the
> >> > options
> >> > to ensure MAC Excel opens the same as PC Excel with SP1? We
currently
> >> > have
> >> > them export to CSV and then open that in excel with the text to
columns
> >> > re-formatting. Any help you could provide would be greatly
> >> > appreciated.
> >>
> >>
> >
> >
>|||In SP1, we support Excel 97 and 2000. You should not get a MIME document
after applying the service pack.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lance" <ldacy@.fellowshiptech.com> wrote in message
news:Og9BSRGgEHA.3964@.TK2MSFTNGP12.phx.gbl...
> The document is garbage...It looks exactly what happens when someone who
> has
> a lower version of excel than XP.
>
> "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> news:enJe9r8fEHA.536@.TK2MSFTNGP11.phx.gbl...
>> So what happens if you open the workbook directly in Excel on the mac
> (don't
>> open it in PC Excel)?
>> --
>> Brian Welcker
>> Group Program Manager
>> SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>> "Lance" <ldacy@.fellowshiptech.com> wrote in message
>> news:ueFapmtfEHA.2848@.TK2MSFTNGP10.phx.gbl...
>> > Yes...It works fine if I save down to Excel 95-2000 workbook and then
> send
>> > it. The mac opens fine, but that is not a viable solution to our
> problem
>> > as
>> > the mac clients will need to run reports on demand. Do you by chance
> know
>> > if there is a solution in the works to ensure MAC Excel versions export
>> > without incidence as the PC version?
>> >
>> > Thanks...
>> >
>> > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
>> > news:Ohc$PCnfEHA.2764@.TK2MSFTNGP11.phx.gbl...
>> >> Have you tried to export the file using a PC, save it to disk and then
>> > open
>> >> it on the Mac? I wouldn't be surprised if there were some glitches.
>> >>
>> >> --
>> >> Brian Welcker
>> >> Group Program Manager
>> >> Microsoft SQL Server Reporting Services
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >>
>> >> "Lance" <Lance@.discussions.microsoft.com> wrote in message
>> >> news:061952A6-F39C-49F3-AA13-F568C4588772@.microsoft.com...
>> >> > We have built a new front end to the report server to run reports.
>> >> > When
>> >> > making calls to the RS Web Service, is there anything special that
>> >> > needs
>> >> > to
>> >> > be done for Excel (xls) rendering? We have a few clients utlizing
>> >> > Apple
>> >> > MAC
>> >> > OS X with Office v.x. We thought that SP1 would take care of their
>> >> > ability
>> >> > to open the xls files as with prior versions of PC xls before Office
>> >> > XP.
>> >> > After further testing, the MAC version still does not open the excel
>> > file
>> >> > correctly. It only has MIME type values in the file. What are the
>> >> > options
>> >> > to ensure MAC Excel opens the same as PC Excel with SP1? We
> currently
>> >> > have
>> >> > them export to CSV and then open that in excel with the text to
> columns
>> >> > re-formatting. Any help you could provide would be greatly
>> >> > appreciated.
>> >>
>> >>
>> >
>> >
>>
>|||I understand that, but the MAC version still gets this MIME document...The
PC version is fine.
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
news:%239umLe7gEHA.3548@.TK2MSFTNGP09.phx.gbl...
> In SP1, we support Excel 97 and 2000. You should not get a MIME document
> after applying the service pack.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Lance" <ldacy@.fellowshiptech.com> wrote in message
> news:Og9BSRGgEHA.3964@.TK2MSFTNGP12.phx.gbl...
> > The document is garbage...It looks exactly what happens when someone who
> > has
> > a lower version of excel than XP.
> >
> >
> > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> > news:enJe9r8fEHA.536@.TK2MSFTNGP11.phx.gbl...
> >> So what happens if you open the workbook directly in Excel on the mac
> > (don't
> >> open it in PC Excel)?
> >>
> >> --
> >> Brian Welcker
> >> Group Program Manager
> >> SQL Server Reporting Services
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> >>
> >> "Lance" <ldacy@.fellowshiptech.com> wrote in message
> >> news:ueFapmtfEHA.2848@.TK2MSFTNGP10.phx.gbl...
> >> > Yes...It works fine if I save down to Excel 95-2000 workbook and then
> > send
> >> > it. The mac opens fine, but that is not a viable solution to our
> > problem
> >> > as
> >> > the mac clients will need to run reports on demand. Do you by chance
> > know
> >> > if there is a solution in the works to ensure MAC Excel versions
export
> >> > without incidence as the PC version?
> >> >
> >> > Thanks...
> >> >
> >> > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
message
> >> > news:Ohc$PCnfEHA.2764@.TK2MSFTNGP11.phx.gbl...
> >> >> Have you tried to export the file using a PC, save it to disk and
then
> >> > open
> >> >> it on the Mac? I wouldn't be surprised if there were some glitches.
> >> >>
> >> >> --
> >> >> Brian Welcker
> >> >> Group Program Manager
> >> >> Microsoft SQL Server Reporting Services
> >> >>
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> > rights.
> >> >>
> >> >> "Lance" <Lance@.discussions.microsoft.com> wrote in message
> >> >> news:061952A6-F39C-49F3-AA13-F568C4588772@.microsoft.com...
> >> >> > We have built a new front end to the report server to run reports.
> >> >> > When
> >> >> > making calls to the RS Web Service, is there anything special that
> >> >> > needs
> >> >> > to
> >> >> > be done for Excel (xls) rendering? We have a few clients utlizing
> >> >> > Apple
> >> >> > MAC
> >> >> > OS X with Office v.x. We thought that SP1 would take care of
their
> >> >> > ability
> >> >> > to open the xls files as with prior versions of PC xls before
Office
> >> >> > XP.
> >> >> > After further testing, the MAC version still does not open the
excel
> >> > file
> >> >> > correctly. It only has MIME type values in the file. What are
the
> >> >> > options
> >> >> > to ensure MAC Excel opens the same as PC Excel with SP1? We
> > currently
> >> >> > have
> >> >> > them export to CSV and then open that in excel with the text to
> > columns
> >> >> > re-formatting. Any help you could provide would be greatly
> >> >> > appreciated.
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>|||Any suggestions or comments?
"Lance" <ldacy@.fellowshiptech.com> wrote in message
news:%23K488YfhEHA.3928@.TK2MSFTNGP11.phx.gbl...
> I understand that, but the MAC version still gets this MIME document...The
> PC version is fine.
>
> "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
> news:%239umLe7gEHA.3548@.TK2MSFTNGP09.phx.gbl...
> > In SP1, we support Excel 97 and 2000. You should not get a MIME document
> > after applying the service pack.
> >
> > --
> > Brian Welcker
> > Group Program Manager
> > Microsoft SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "Lance" <ldacy@.fellowshiptech.com> wrote in message
> > news:Og9BSRGgEHA.3964@.TK2MSFTNGP12.phx.gbl...
> > > The document is garbage...It looks exactly what happens when someone
who
> > > has
> > > a lower version of excel than XP.
> > >
> > >
> > > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
message
> > > news:enJe9r8fEHA.536@.TK2MSFTNGP11.phx.gbl...
> > >> So what happens if you open the workbook directly in Excel on the mac
> > > (don't
> > >> open it in PC Excel)?
> > >>
> > >> --
> > >> Brian Welcker
> > >> Group Program Manager
> > >> SQL Server Reporting Services
> > >>
> > >> This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > >>
> > >> "Lance" <ldacy@.fellowshiptech.com> wrote in message
> > >> news:ueFapmtfEHA.2848@.TK2MSFTNGP10.phx.gbl...
> > >> > Yes...It works fine if I save down to Excel 95-2000 workbook and
then
> > > send
> > >> > it. The mac opens fine, but that is not a viable solution to our
> > > problem
> > >> > as
> > >> > the mac clients will need to run reports on demand. Do you by
chance
> > > know
> > >> > if there is a solution in the works to ensure MAC Excel versions
> export
> > >> > without incidence as the PC version?
> > >> >
> > >> > Thanks...
> > >> >
> > >> > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
> message
> > >> > news:Ohc$PCnfEHA.2764@.TK2MSFTNGP11.phx.gbl...
> > >> >> Have you tried to export the file using a PC, save it to disk and
> then
> > >> > open
> > >> >> it on the Mac? I wouldn't be surprised if there were some
glitches.
> > >> >>
> > >> >> --
> > >> >> Brian Welcker
> > >> >> Group Program Manager
> > >> >> Microsoft SQL Server Reporting Services
> > >> >>
> > >> >> This posting is provided "AS IS" with no warranties, and confers
no
> > >> > rights.
> > >> >>
> > >> >> "Lance" <Lance@.discussions.microsoft.com> wrote in message
> > >> >> news:061952A6-F39C-49F3-AA13-F568C4588772@.microsoft.com...
> > >> >> > We have built a new front end to the report server to run
reports.
> > >> >> > When
> > >> >> > making calls to the RS Web Service, is there anything special
that
> > >> >> > needs
> > >> >> > to
> > >> >> > be done for Excel (xls) rendering? We have a few clients
utlizing
> > >> >> > Apple
> > >> >> > MAC
> > >> >> > OS X with Office v.x. We thought that SP1 would take care of
> their
> > >> >> > ability
> > >> >> > to open the xls files as with prior versions of PC xls before
> Office
> > >> >> > XP.
> > >> >> > After further testing, the MAC version still does not open the
> excel
> > >> > file
> > >> >> > correctly. It only has MIME type values in the file. What are
> the
> > >> >> > options
> > >> >> > to ensure MAC Excel opens the same as PC Excel with SP1? We
> > > currently
> > >> >> > have
> > >> >> > them export to CSV and then open that in excel with the text to
> > > columns
> > >> >> > re-formatting. Any help you could provide would be greatly
> > >> >> > appreciated.
> > >> >>
> > >> >>
> > >> >
> > >> >
> > >>
> > >>
> > >
> > >
> >
> >
>|||We aren't generating MIME any more. That code is gone. Something else must
be wrong with the file type. We will take a look but it is not a highly
demanded scenario.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lance" <ldacy@.fellowshiptech.com> wrote in message
news:%23FHK6dSiEHA.2952@.TK2MSFTNGP09.phx.gbl...
> Any suggestions or comments?
>
> "Lance" <ldacy@.fellowshiptech.com> wrote in message
> news:%23K488YfhEHA.3928@.TK2MSFTNGP11.phx.gbl...
>> I understand that, but the MAC version still gets this MIME
>> document...The
>> PC version is fine.
>>
>> "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message
>> news:%239umLe7gEHA.3548@.TK2MSFTNGP09.phx.gbl...
>> > In SP1, we support Excel 97 and 2000. You should not get a MIME
>> > document
>> > after applying the service pack.
>> >
>> > --
>> > Brian Welcker
>> > Group Program Manager
>> > Microsoft SQL Server Reporting Services
>> >
>> > This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> >
>> > "Lance" <ldacy@.fellowshiptech.com> wrote in message
>> > news:Og9BSRGgEHA.3964@.TK2MSFTNGP12.phx.gbl...
>> > > The document is garbage...It looks exactly what happens when someone
> who
>> > > has
>> > > a lower version of excel than XP.
>> > >
>> > >
>> > > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
> message
>> > > news:enJe9r8fEHA.536@.TK2MSFTNGP11.phx.gbl...
>> > >> So what happens if you open the workbook directly in Excel on the
>> > >> mac
>> > > (don't
>> > >> open it in PC Excel)?
>> > >>
>> > >> --
>> > >> Brian Welcker
>> > >> Group Program Manager
>> > >> SQL Server Reporting Services
>> > >>
>> > >> This posting is provided "AS IS" with no warranties, and confers no
>> > > rights.
>> > >>
>> > >> "Lance" <ldacy@.fellowshiptech.com> wrote in message
>> > >> news:ueFapmtfEHA.2848@.TK2MSFTNGP10.phx.gbl...
>> > >> > Yes...It works fine if I save down to Excel 95-2000 workbook and
> then
>> > > send
>> > >> > it. The mac opens fine, but that is not a viable solution to our
>> > > problem
>> > >> > as
>> > >> > the mac clients will need to run reports on demand. Do you by
> chance
>> > > know
>> > >> > if there is a solution in the works to ensure MAC Excel versions
>> export
>> > >> > without incidence as the PC version?
>> > >> >
>> > >> > Thanks...
>> > >> >
>> > >> > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in
>> message
>> > >> > news:Ohc$PCnfEHA.2764@.TK2MSFTNGP11.phx.gbl...
>> > >> >> Have you tried to export the file using a PC, save it to disk and
>> then
>> > >> > open
>> > >> >> it on the Mac? I wouldn't be surprised if there were some
> glitches.
>> > >> >>
>> > >> >> --
>> > >> >> Brian Welcker
>> > >> >> Group Program Manager
>> > >> >> Microsoft SQL Server Reporting Services
>> > >> >>
>> > >> >> This posting is provided "AS IS" with no warranties, and confers
> no
>> > >> > rights.
>> > >> >>
>> > >> >> "Lance" <Lance@.discussions.microsoft.com> wrote in message
>> > >> >> news:061952A6-F39C-49F3-AA13-F568C4588772@.microsoft.com...
>> > >> >> > We have built a new front end to the report server to run
> reports.
>> > >> >> > When
>> > >> >> > making calls to the RS Web Service, is there anything special
> that
>> > >> >> > needs
>> > >> >> > to
>> > >> >> > be done for Excel (xls) rendering? We have a few clients
> utlizing
>> > >> >> > Apple
>> > >> >> > MAC
>> > >> >> > OS X with Office v.x. We thought that SP1 would take care of
>> their
>> > >> >> > ability
>> > >> >> > to open the xls files as with prior versions of PC xls before
>> Office
>> > >> >> > XP.
>> > >> >> > After further testing, the MAC version still does not open the
>> excel
>> > >> > file
>> > >> >> > correctly. It only has MIME type values in the file. What are
>> the
>> > >> >> > options
>> > >> >> > to ensure MAC Excel opens the same as PC Excel with SP1? We
>> > > currently
>> > >> >> > have
>> > >> >> > them export to CSV and then open that in excel with the text to
>> > > columns
>> > >> >> > re-formatting. Any help you could provide would be greatly
>> > >> >> > appreciated.
>> > >> >>
>> > >> >>
>> > >> >
>> > >> >
>> > >>
>> > >>
>> > >
>> > >
>> >
>> >
>>
>