Excel format

Hi,
Anyone know how can I export data to Excel 97/2000?,
because in my company everybody has Excel 97/2000 and it's
impossible change version.
Thanks and sory for my English :)Install SP1. From SP1 Readme:
<
Rendered reports can now be opened in Excel 97 and later. Previously, the
file format was MIME Encapsulation of Aggregate HTML (MHTML), which could
only be opened in Excel 2002 and later. The format for rendered reports is
now Binary Interchange File Format (BIFF), which can be opened in Excel 97
and later.
/>
--
Ravi Mumulla (Microsoft)
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
<jcrf@.discussions.microsoft.com> wrote in message
news:3c5c01c4ac41$35d10900$a501280a@.phx.gbl...
> Hi,
> Anyone know how can I export data to Excel 97/2000?,
> because in my company everybody has Excel 97/2000 and it's
> impossible change version.
> Thanks and sory for my English :)

Excel files are too large

I have the following problem with Reporting Services:
My report has about 6500 lines and 100 columns. When I export it into Excel
the size of the end file is about 20 Mb. As I have to send it using
subscriptions, it is a problem â' too large file for e-mail. Are there any
ways to minimize the size of output Excel file?
Regards,
Boris.Workaround:
Create a webpage containing your report, post it on the webserver, and
e-mail a link to this page to your customer.
It is faster, and more friendly designed ( and it began to be a
standard in modern distributed applications)
You also have to take care about "Garbage Collection": set an
expiration date for reports to be deleted from the webserver.
Have fun :)|||Are you using Service Pack 1? We did some sizing work but it still might be
too big for you.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Boris" <frolovBA@.trytoguessHM.com> wrote in message
news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
>I have the following problem with Reporting Services:
> My report has about 6500 lines and 100 columns. When I export it into
> Excel
> the size of the end file is about 20 Mb. As I have to send it using
> subscriptions, it is a problem - too large file for e-mail. Are there any
> ways to minimize the size of output Excel file?
> Regards,
> Boris.
>|||Thank you for your advice, but users of this report want to receive it in
Excel.
Iâ've made a workaround: Reporting Services save the Excel file into
directory and then my program archive it and send it through e-mail. But may
be I miss some details that can optimize the size of Report?
Regards,
Boris
"katzirina" wrote:
> Workaround:
> Create a webpage containing your report, post it on the webserver, and
> e-mail a link to this page to your customer.
> It is faster, and more friendly designed ( and it began to be a
> standard in modern distributed applications)
> You also have to take care about "Garbage Collection": set an
> expiration date for reports to be deleted from the webserver.
> Have fun :)
>|||Yes I use SP1.
Regards,
Boris.
"Brian Welcker [MS]" wrote:
> Are you using Service Pack 1? We did some sizing work but it still might be
> too big for you.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
> news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
> >I have the following problem with Reporting Services:
> > My report has about 6500 lines and 100 columns. When I export it into
> > Excel
> > the size of the end file is about 20 Mb. As I have to send it using
> > subscriptions, it is a problem - too large file for e-mail. Are there any
> > ways to minimize the size of output Excel file?
> >
> > Regards,
> > Boris.
> >
>
>|||When you create the spreadsheet manually, how large is it? I just tried a
very simple sheet with no formatting and a single number per cell and it was
5 MB. The only way this would work through compression in the delivery
provider. We do not support this but there might be a 3rd party that does.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Boris" <frolovBA@.trytoguessHM.com> wrote in message
news:6A26B3A5-0CF5-4F3B-8B1A-3CB4F36B453E@.microsoft.com...
> Yes I use SP1.
> Regards,
> Boris.
> "Brian Welcker [MS]" wrote:
>> Are you using Service Pack 1? We did some sizing work but it still might
>> be
>> too big for you.
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
>> news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
>> >I have the following problem with Reporting Services:
>> > My report has about 6500 lines and 100 columns. When I export it into
>> > Excel
>> > the size of the end file is about 20 Mb. As I have to send it using
>> > subscriptions, it is a problem - too large file for e-mail. Are there
>> > any
>> > ways to minimize the size of output Excel file?
>> >
>> > Regards,
>> > Boris.
>> >
>>|||When I create it manually itâ's about 6 Mb. Even if I made export to Excel
from Reporting Server, then open this 24 Mb file and save it â' it gets size
about 7 Mb. The only formatting I use are 0.5pt borders and number/date
formats.
Regards,
Boris.
"Brian Welcker [MS]" wrote:
> When you create the spreadsheet manually, how large is it? I just tried a
> very simple sheet with no formatting and a single number per cell and it was
> 5 MB. The only way this would work through compression in the delivery
> provider. We do not support this but there might be a 3rd party that does.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
> news:6A26B3A5-0CF5-4F3B-8B1A-3CB4F36B453E@.microsoft.com...
> > Yes I use SP1.
> >
> > Regards,
> > Boris.
> >
> > "Brian Welcker [MS]" wrote:
> >
> >> Are you using Service Pack 1? We did some sizing work but it still might
> >> be
> >> too big for you.
> >>
> >> --
> >> Brian Welcker
> >> Group Program Manager
> >> Microsoft SQL Server
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Boris" <frolovBA@.trytoguessHM.com> wrote in message
> >> news:CBAA6D77-E111-469F-8261-C0CC9A78A82B@.microsoft.com...
> >> >I have the following problem with Reporting Services:
> >> > My report has about 6500 lines and 100 columns. When I export it into
> >> > Excel
> >> > the size of the end file is about 20 Mb. As I have to send it using
> >> > subscriptions, it is a problem - too large file for e-mail. Are there
> >> > any
> >> > ways to minimize the size of output Excel file?
> >> >
> >> > Regards,
> >> > Boris.
> >> >
> >>
> >>
> >>
>
>

Excel Export-Extra columns

Hi,
I am trying to export my report to Excel.When I do this I get some extra columns(blank though) in the Excel sheet which r not there in my report.And I see some greentips in some of my cells in excel sheet(which is a warning that a number is exported as text).Why r this due to?How can i remove these?
Thank You,When you are using a list in your report, this will most likely happen as we
have to approximate the cell layout. Table and matrix work much better when
exporting. Also, make sure you have number formats on your values so they
will get explicit formats in Excel.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sudha" <Sudha@.discussions.microsoft.com> wrote in message
news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
> Hi,
> I am trying to export my report to Excel.When I do this I get some extra
> columns(blank though) in the Excel sheet which r not there in my
> report.And I see some greentips in some of my cells in excel sheet(which
> is a warning that a number is exported as text).Why r this due to?How can
> i remove these?
> Thank You,|||Hi,
I am using only tables/matrix in my reports and not lists still i get some extra columns.How can i avoid this?
Thanx
"Brian Welcker [MSFT]" wrote:
> When you are using a list in your report, this will most likely happen as we
> have to approximate the cell layout. Table and matrix work much better when
> exporting. Also, make sure you have number formats on your values so they
> will get explicit formats in Excel.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
> news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
> > Hi,
> >
> > I am trying to export my report to Excel.When I do this I get some extra
> > columns(blank though) in the Excel sheet which r not there in my
> > report.And I see some greentips in some of my cells in excel sheet(which
> > is a warning that a number is exported as text).Why r this due to?How can
> > i remove these?
> >
> > Thank You,
>
>|||Do you have page headers and footers? This can cause this as well. And when
you say you have tables / matrices, you mean in different reports, right? If
this is not the case, it would be interesting to see your reports and the
Excel output.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Sudha" <Sudha@.discussions.microsoft.com> wrote in message
news:53373429-2B5D-4335-8113-819A969B3C15@.microsoft.com...
> Hi,
> I am using only tables/matrix in my reports and not lists still i get some
> extra columns.How can i avoid this?
> Thanx
> "Brian Welcker [MSFT]" wrote:
>> When you are using a list in your report, this will most likely happen as
>> we
>> have to approximate the cell layout. Table and matrix work much better
>> when
>> exporting. Also, make sure you have number formats on your values so they
>> will get explicit formats in Excel.
>> --
>> Brian Welcker
>> Group Program Manager
>> SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
>> news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
>> > Hi,
>> >
>> > I am trying to export my report to Excel.When I do this I get some
>> > extra
>> > columns(blank though) in the Excel sheet which r not there in my
>> > report.And I see some greentips in some of my cells in excel
>> > sheet(which
>> > is a warning that a number is exported as text).Why r this due to?How
>> > can
>> > i remove these?
>> >
>> > Thank You,
>>|||I am using a table for my report and I'm not implementing a header nor
a footer. In the end of the table though, I used a line and a textbox
to somehow "appear as a footer" at the end of the report.
Upon export to excel, extra columns were inserted and I don't know how
does this happened or how I can remove them.
I'll be more than willing to provide you with screenshots of the
report in the designer view and its output in excel.
I hope you can advice me on this matter and any help will be greatly
appreciated.
Have a nice day and thanks in advance.
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> wrote in message news:<uh5BAZMYEHA.3260@.tk2msftngp13.phx.gbl>...
> Do you have page headers and footers? This can cause this as well. And when
> you say you have tables / matrices, you mean in different reports, right? If
> this is not the case, it would be interesting to see your reports and the
> Excel output.
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
> news:53373429-2B5D-4335-8113-819A969B3C15@.microsoft.com...
> > Hi,
> >
> > I am using only tables/matrix in my reports and not lists still i get some
> > extra columns.How can i avoid this?
> >
> > Thanx
> >
> > "Brian Welcker [MSFT]" wrote:
> >
> >> When you are using a list in your report, this will most likely happen as
> >> we
> >> have to approximate the cell layout. Table and matrix work much better
> >> when
> >> exporting. Also, make sure you have number formats on your values so they
> >> will get explicit formats in Excel.
> >>
> >> --
> >> Brian Welcker
> >> Group Program Manager
> >> SQL Server Reporting Services
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Sudha" <Sudha@.discussions.microsoft.com> wrote in message
> >> news:D67121D5-E109-448E-AE9A-5866EDCDD18F@.microsoft.com...
> >> > Hi,
> >> >
> >> > I am trying to export my report to Excel.When I do this I get some
> >> > extra
> >> > columns(blank though) in the Excel sheet which r not there in my
> >> > report.And I see some greentips in some of my cells in excel
> >> > sheet(which
> >> > is a warning that a number is exported as text).Why r this due to?How
> >> > can
> >> > i remove these?
> >> >
> >> > Thank You,
> >>
> >>
> >>

Excel Export: How to force SSRS to generate Excel AVG and SUM formulas?

Hi
We are using SSRS 2005 to generate excel sheets. At this point we need to
have Excel SUM and AVG functionality in the exported Excel sheets, but SSRS
puts the resulting number instead of the actual formula. The problem is that
when end user modifies data, the SUM and AVG fields don't update according
to the changes.
Is there any way to force SSRS to generate SUM and AVG formulas instead of
generating the result numbers?
Any help would be appreciated,
MaxHello Max,
This issue is a limitation in the current Reporting Services. Better
formula support is on our wishlist for a future release.
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
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.)

excel export...

Hi Guys
When exporting my report to excel my field text gets exported as double
lines. Does anybody know a way around this?
eg:
Line 1
Line 2
turns to
Line 1
Line 2
Thanks
KezHi,
If the space between two rows are more than 0.125 in, then this is the limit
it removes automatically when export to excel. Try reducing your row height
and see how excel renders.
Amarnath.
"Kez" wrote:
> Hi Guys
> When exporting my report to excel my field text gets exported as double
> lines. Does anybody know a way around this?
> eg:
> Line 1
> Line 2
> turns to
> Line 1
> Line 2
>
> Thanks
> Kez|||Thanks
That did the trick
"Amarnath" wrote:
> Hi,
> If the space between two rows are more than 0.125 in, then this is the limit
> it removes automatically when export to excel. Try reducing your row height
> and see how excel renders.
> Amarnath.
>
> "Kez" wrote:
> > Hi Guys
> > When exporting my report to excel my field text gets exported as double
> > lines. Does anybody know a way around this?
> >
> > eg:
> > Line 1
> > Line 2
> >
> > turns to
> > Line 1
> >
> > Line 2
> >
> >
> > Thanks
> > Kez

Excel export with formulas

Hi All
Just wondering if there is an option to turn of the exporting of formulas to
Excel, or alternatively not having it create named ranges for the formulas.
I have one report that frequently has over 5500 rows and 5 columns, the last
two are formulas for calculating percentage of the total.
This results in around 20000 named ranges which makes it incredibly slow
(15-20 seconds) to open the workbook.
Thanks
PhillYou can set OmitFormulas in device info to turn off formulas.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSCREATE/htm/rcr_creating_dc_v1_4d0x.asp
Fang Wang (MSFT)
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Phill Carter" <pcarter@.no-spam.bellpotter.com.au> wrote in message
news:%23oti9n8XEHA.1000@.TK2MSFTNGP12.phx.gbl...
> Hi All
> Just wondering if there is an option to turn of the exporting of formulas
to
> Excel, or alternatively not having it create named ranges for the
formulas.
> I have one report that frequently has over 5500 rows and 5 columns, the
last
> two are formulas for calculating percentage of the total.
> This results in around 20000 named ranges which makes it incredibly slow
> (15-20 seconds) to open the workbook.
> Thanks
> Phill
>|||So how do I specify the OmitFormulas device info in a subscription?
Thanks
Phill
"Fang Wang (MSFT)" <fangw@.microsoft.com> wrote in message
news:Op1S2ZJYEHA.2812@.TK2MSFTNGP11.phx.gbl...
> You can set OmitFormulas in device info to turn off formulas.
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSCREATE/htm/rcr_creating_dc_v1_4d0x.asp
> Fang Wang (MSFT)
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "Phill Carter" <pcarter@.no-spam.bellpotter.com.au> wrote in message
> news:%23oti9n8XEHA.1000@.TK2MSFTNGP12.phx.gbl...
> > Hi All
> >
> > Just wondering if there is an option to turn of the exporting of
formulas
> to
> > Excel, or alternatively not having it create named ranges for the
> formulas.
> >
> > I have one report that frequently has over 5500 rows and 5 columns, the
> last
> > two are formulas for calculating percentage of the total.
> >
> > This results in around 20000 named ranges which makes it incredibly slow
> > (15-20 seconds) to open the workbook.
> >
> > Thanks
> > Phill
> >
> >
>

Excel Export Troubles

I have a local report that I am trying to export to Excel. It uses a stored procedure( SQL 2005) as the data source. The stored procedure runs in 2 seconds and returns about 8000 rows. The export to excel never completes(does work if I limit the number of rows returned). I have set the executionTimeout="36000" in the web.config and set the table adapters Command timeout in the code high enough so that I am not getting timeout errors. The export to PDF works, though takes a few minutes. Looking for any thoughts or ideas on why Excel is so slow.

Here is one idea. Use a SqlDataAdapter and fill a DataSet using your Store Proc then use this free dll to export the DataSet data into CSV file. Excel can easily read the csv and you can format the report in any way you need to.

Here is the link: http://apriendavisualstudio.net/?p=23

Try it, it very simple nothing fancy. It works for me.

sql

Excel Export Report Footer Problem

We have a footer in our reports which displays a disclaimer in a textbox.
The disclaimer shows up fine when exported to PDF, but when exported to Excel
it chops off everything but the first 255 chars. Can someone explain why
this is happening?Frank,
How do you hide Footer for Browser/Web View and enable it only for Email
Subscription ( Email / Pdf / MHTML ) format. Is it possible to add Disclaimer
text on the Create Subscription Web method.
Let me know pls.
Thanks!
"Frank Hoover" wrote:
> We have a footer in our reports which displays a disclaimer in a textbox.
> The disclaimer shows up fine when exported to PDF, but when exported to Excel
> it chops off everything but the first 255 chars. Can someone explain why
> this is happening?|||I read in the documentation that excel has a limit of 255 characters for the
footer - looks like you hit the limit.
"Frank Hoover" wrote:
> We have a footer in our reports which displays a disclaimer in a textbox.
> The disclaimer shows up fine when exported to PDF, but when exported to Excel
> it chops off everything but the first 255 chars. Can someone explain why
> this is happening?

Excel export problems

Hi,

I am a beginner using Sql server 2000 with visualstudionet 2003. When I try to export a report to excel spreadsheet. some of the page headers are displaying in separate row. page headers seems to align perfectly with the table columns and they seem fine in preview. Can someone help me with this issue.

Thanks

Bhavya

How are you doing the export ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

I am exporting from Report Manager. Thanks for the resposne.

Bhavya

|||Its hard to tell without having you report design at hand, my suggestion would be to inspect the controls used one by one and eventually create a new report with importing the controls one by one.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Excel export problem

Maybe others have had this similar problem and can give me a hint on how to resolve it...
I have a text box across the top of a report that is causing merged columns when the report is exported to Excel. It's making my users unable to sort the exported table without great difficulty.
What options may I have for putting a title along the top and still now have to worry about the merged columns in Excel?
Thanks much in advance...Troy

Hello,

Excel renderer will try to preserve the layout of you report. As long as your Title will span multiple table columns (at design time) you will have the problem.

Can you use on single cell for your Title or split it between multiple rows?

Thank you,

Nico

Excel export problem

I have a report that the users want to export to Excel. One of the problems that I am having is that some of the cells in the excel export are renamed as _402, _404, etc. I want them to come in as B22, B24, etc. Any idea why this is happening and how I can stop it?

Joe

The Excel renderer gives unique names to cells that are the operands of formulas. Then, the formulas reference those unique names instead of the cell addresses. This is by design and there is currently no way to export live Excel formulas without using those unique names. That feature is on our list of hopeful features for a future release.

If you want to get rid of formula export entirely and just have the calculated values put into the cells, you can OmitFormulas DeviceInfo parameter:

http://msdn2.microsoft.com/en-us/library/ms159220.aspx

Best,
-Chris

|||

OK, I can see that, but how can I affect all Excel exports from the report viewer? Do I set a parameter in the report server config file? Thanks for the info.

Joe

Excel Export problem

Hello,
I am trying to export some reports to excel format, using Reporting Services
SP1. It contains an OLAP query and a matrix allowing drill-down.
Reporting services errors with:
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown. (rrRenderingError) Get Online Help
Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown.
Object reference not set to an instance of an object.
An anyone help?
Thanks.
Ben.Can you post some code?
Dave
"Ben Mann" <BenMann@.discussions.microsoft.com> wrote in message
news:976C1E52-2D9F-4EA3-AC3E-1D7440B8FAB3@.microsoft.com...
> Hello,
> I am trying to export some reports to excel format, using Reporting
> Services
> SP1. It contains an OLAP query and a matrix allowing drill-down.
> Reporting services errors with:
> Exception of type
> Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
> thrown. (rrRenderingError) Get Online Help
> Exception of type
> Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
> thrown.
> Object reference not set to an instance of an object.
> An anyone help?
> Thanks.
> Ben.|||Hello,
Im not sure how much help this might be, but this is the rdl source for the
report...
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<rd:GridSpacing>0.25cm</rd:GridSpacing>
<RightMargin>2.5cm</RightMargin>
<Body>
<ReportItems>
<Textbox Name="textbox3">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<FontSize>8pt</FontSize>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<ZIndex>3</ZIndex>
<Top>1.82275cm</Top>
<rd:DefaultName>textbox3</rd:DefaultName>
<Height>0.5cm</Height>
<Width>9.75cm</Width>
<CanGrow>true</CanGrow>
<Value>="Team: " + Parameters!ReportTeam.Label</Value>
<Left>0.25cm</Left>
</Textbox>
<Textbox Name="ParameterDisplayYear">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<FontSize>8pt</FontSize>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<ZIndex>2</ZIndex>
<Top>1.32275cm</Top>
<Height>0.5cm</Height>
<Width>14cm</Width>
<CanGrow>true</CanGrow>
<Value>="Year: " + Parameters!ReportYear.Value</Value>
<Left>0.25cm</Left>
</Textbox>
<Matrix Name="matrix1">
<Corner>
<ReportItems>
<Textbox Name="textbox1">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<ZIndex>12</ZIndex>
<rd:DefaultName>textbox1</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value />
</Textbox>
</ReportItems>
</Corner>
<Height>2.5cm</Height>
<ZIndex>1</ZIndex>
<Style />
<MatrixRows>
<MatrixRow>
<MatrixCells>
<MatrixCell>
<ReportItems>
<Textbox Name="Measures_Leavers">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<TextAlign>Right</TextAlign>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<ZIndex>2</ZIndex>
<rd:DefaultName>Measures_Leavers</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value>=Sum(Fields!Measures_Leavers.Value)</Value>
</Textbox>
</ReportItems>
</MatrixCell>
<MatrixCell>
<ReportItems>
<Textbox Name="Measures_Total_Sales">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<TextAlign>Right</TextAlign>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<ZIndex>1</ZIndex>
<rd:DefaultName>Measures_Total_Sales</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value>=Sum(Fields!Measures_Total_Sales.Value)</Value>
</Textbox>
</ReportItems>
</MatrixCell>
<MatrixCell>
<ReportItems>
<Textbox Name="textbox2">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<Format>P</Format>
<FontFamily>Verdana</FontFamily>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<TextAlign>Right</TextAlign>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<CanGrow>true</CanGrow>
<Value>=iIF(Sum(Fields!Measures_Leavers.Value) /
Sum(Fields!Measures_Total_Sales.Value) > 0,
Sum(Fields!Measures_Leavers.Value) / Sum(Fields!Measures_Total_Sales.Value),
0)</Value>
</Textbox>
</ReportItems>
</MatrixCell>
</MatrixCells>
<Height>0.5cm</Height>
</MatrixRow>
</MatrixRows>
<MatrixColumns>
<MatrixColumn>
<Width>2.55291cm</Width>
</MatrixColumn>
<MatrixColumn>
<Width>2.75cm</Width>
</MatrixColumn>
<MatrixColumn>
<Width>2.5cm</Width>
</MatrixColumn>
</MatrixColumns>
<DataSetName>LeaversSummary</DataSetName>
<ColumnGroupings>
<ColumnGrouping>
<DynamicColumns>
<Grouping Name="matrix1_PopulationDate_Year">
<GroupExpressions>
<GroupExpression>=Fields!PopulationDate_Year.Value</GroupExpression>
</GroupExpressions>
</Grouping>
<ReportItems>
<Textbox Name="PopulationDate_Year">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<BackgroundColor>#b5ddad</BackgroundColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<TextAlign>Center</TextAlign>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
<FontWeight>700</FontWeight>
</Style>
<ZIndex>11</ZIndex>
<rd:DefaultName>PopulationDate_Year</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value>=Fields!PopulationDate_Year.Value</Value>
</Textbox>
</ReportItems>
</DynamicColumns>
<Height>0.5cm</Height>
</ColumnGrouping>
<ColumnGrouping>
<DynamicColumns>
<Grouping Name="matrix1_ColumnGroup2">
<GroupExpressions>
<GroupExpression>=Fields!PopulationDate_Quarter.Value</GroupExpression>
</GroupExpressions>
</Grouping>
<Visibility>
<ToggleItem>PopulationDate_Year</ToggleItem>
<Hidden>true</Hidden>
</Visibility>
<ReportItems>
<Textbox Name="PopulationDate_Quarter">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<BackgroundColor>#b5ddad</BackgroundColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<TextAlign>Center</TextAlign>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
<FontWeight>700</FontWeight>
</Style>
<ZIndex>10</ZIndex>
<CanGrow>true</CanGrow>
<Value>=Fields!PopulationDate_Quarter.Value</Value>
</Textbox>
</ReportItems>
</DynamicColumns>
<Height>0.5cm</Height>
</ColumnGrouping>
<ColumnGrouping>
<DynamicColumns>
<Grouping Name="matrix1_ColumnGroup3">
<GroupExpressions>
<GroupExpression>=Fields!PopulationDate_Month.Value</GroupExpression>
</GroupExpressions>
</Grouping>
<Visibility>
<ToggleItem>PopulationDate_Quarter</ToggleItem>
<Hidden>true</Hidden>
</Visibility>
<ReportItems>
<Textbox Name="PopulationDate_Month">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<BackgroundColor>#b5ddad</BackgroundColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<TextAlign>Center</TextAlign>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
<FontWeight>700</FontWeight>
</Style>
<ZIndex>9</ZIndex>
<CanGrow>true</CanGrow>
<Value>=MonthName(Fields!PopulationDate_Month.Value,
true)</Value>
</Textbox>
</ReportItems>
</DynamicColumns>
<Height>0.5cm</Height>
</ColumnGrouping>
<ColumnGrouping>
<Height>0.5cm</Height>
<StaticColumns>
<StaticColumn>
<ReportItems>
<Textbox Name="textbox4">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<BackgroundColor>#b5ddad</BackgroundColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<TextAlign>Right</TextAlign>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
<FontWeight>700</FontWeight>
</Style>
<ZIndex>8</ZIndex>
<rd:DefaultName>textbox4</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value>Leavers</Value>
</Textbox>
</ReportItems>
</StaticColumn>
<StaticColumn>
<ReportItems>
<Textbox Name="textbox7">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<BackgroundColor>#b5ddad</BackgroundColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<TextAlign>Right</TextAlign>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
<FontWeight>700</FontWeight>
</Style>
<ZIndex>7</ZIndex>
<rd:DefaultName>textbox7</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value>Total Sales</Value>
</Textbox>
</ReportItems>
</StaticColumn>
<StaticColumn>
<ReportItems>
<Textbox Name="textbox8">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<BackgroundColor>#b5ddad</BackgroundColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<TextAlign>Right</TextAlign>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
<FontWeight>700</FontWeight>
</Style>
<ZIndex>6</ZIndex>
<rd:DefaultName>textbox8</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value>Leavers (%)</Value>
</Textbox>
</ReportItems>
</StaticColumn>
</StaticColumns>
</ColumnGrouping>
</ColumnGroupings>
<Width>14.05291cm</Width>
<Top>2.32275cm</Top>
<Left>0.25cm</Left>
<RowGroupings>
<RowGrouping>
<DynamicRows>
<Grouping Name="matrix1_Consultant_Sales_Team">
<GroupExpressions>
<GroupExpression>=Fields!Consultant_Sales_Team.Value</GroupExpression>
</GroupExpressions>
</Grouping>
<ReportItems>
<Textbox Name="Consultant_Sales_Team">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<BackgroundColor>#99ccff</BackgroundColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
<FontWeight>700</FontWeight>
</Style>
<ZIndex>5</ZIndex>
<rd:DefaultName>Consultant_Sales_Team</rd:DefaultName>
<CanGrow>true</CanGrow>
<Value>=Fields!Consultant_Sales_Team.Value</Value>
</Textbox>
</ReportItems>
</DynamicRows>
<Width>2.25cm</Width>
</RowGrouping>
<RowGrouping>
<DynamicRows>
<Grouping Name="matrix1_RowGroup2">
<GroupExpressions>
<GroupExpression>=Fields!Consultant_Name.Value</GroupExpression>
</GroupExpressions>
</Grouping>
<Visibility>
<ToggleItem>Consultant_Sales_Team</ToggleItem>
<Hidden>true</Hidden>
</Visibility>
<ReportItems>
<Textbox Name="Consultant_Name">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<BackgroundColor>#99ccff</BackgroundColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
<FontWeight>700</FontWeight>
</Style>
<ZIndex>4</ZIndex>
<CanGrow>true</CanGrow>
<Value>=Fields!Consultant_Name.Value</Value>
</Textbox>
</ReportItems>
</DynamicRows>
<Width>2.75cm</Width>
</RowGrouping>
<RowGrouping>
<DynamicRows>
<Grouping Name="matrix1_RowGroup3">
<GroupExpressions>
<GroupExpression>=Fields!Consultant_Post_Code_Area.Value</GroupExpression>
</GroupExpressions>
</Grouping>
<Visibility>
<ToggleItem>Consultant_Name</ToggleItem>
<Hidden>true</Hidden>
</Visibility>
<ReportItems>
<Textbox Name="Consultant_PostcodeArea">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<FontFamily>Verdana</FontFamily>
<BackgroundColor>#99ccff</BackgroundColor>
<BorderStyle>
<Default>Solid</Default>
</BorderStyle>
<FontSize>8pt</FontSize>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
<FontWeight>700</FontWeight>
</Style>
<ZIndex>3</ZIndex>
<CanGrow>true</CanGrow>
<Value>=Fields!Consultant_Post_Code_Area.Value</Value>
</Textbox>
</ReportItems>
</DynamicRows>
<Width>1.25cm</Width>
</RowGrouping>
</RowGroupings>
</Matrix>
<Image Name="image1">
<MIMEType />
<Height>1.32275cm</Height>
<Width>7.93651cm</Width>
<Source>External</Source>
<Style />
<Value>leaverssummarybyteam.gif</Value>
<Left>0.25cm</Left>
<ToolTip>Leavers Summary by Team</ToolTip>
<Sizing>AutoSize</Sizing>
</Image>
</ReportItems>
<Style />
<Height>5.25cm</Height>
<ColumnSpacing>1cm</ColumnSpacing>
</Body>
<TopMargin>2.5cm</TopMargin>
<DataSources>
<DataSource Name="MIS">
<rd:DataSourceID>922803da-5239-4648-8a28-ec0db0f80d99</rd:DataSourceID>
<DataSourceReference>MIS</DataSourceReference>
</DataSource>
</DataSources>
<Width>14.75cm</Width>
<DataSets>
<DataSet Name="LeaversSummary">
<Fields>
<Field Name="PopulationDate_Year">
<DataField>[PopulationDate].[Year].[MEMBER_CAPTION]</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="PopulationDate_Quarter">
<DataField>[PopulationDate].[Quarter].[MEMBER_CAPTION]</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="PopulationDate_Month">
<DataField>[PopulationDate].[Month].[MEMBER_CAPTION]</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="Consultant_Sales_Team">
<DataField>[Consultant].[Sales Team].[MEMBER_CAPTION]</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="Consultant_Type">
<DataField>[Consultant].[Type].[MEMBER_CAPTION]</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="Consultant_Name">
<DataField>[Consultant].[Name].[MEMBER_CAPTION]</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="Consultant_Post_Code_Area">
<DataField>[Consultant].[Post Code
Area].[MEMBER_CAPTION]</DataField>
<rd:TypeName>System.String</rd:TypeName>
</Field>
<Field Name="Measures_Leavers">
<DataField>[Measures].[Leavers]</DataField>
<rd:TypeName>System.Object</rd:TypeName>
</Field>
<Field Name="Measures_Total_Sales">
<DataField>[Measures].[Total Sales]</DataField>
<rd:TypeName>System.Object</rd:TypeName>
</Field>
<Field Name="Measures__Leavers">
<DataField>[Measures].[%Leavers]</DataField>
<rd:TypeName>System.Object</rd:TypeName>
</Field>
</Fields>
<Query>
<DataSourceName>MIS</DataSourceName>
<CommandText>= "SELECT { [Measures].[Leavers], [Measures].[Total
Sales], [Measures].[%Leavers] } ON COLUMNS, { Descendants([Consultant].[" +
Parameters!ReportTeam.Value + "], [Consultant].[Post Code Area], LEAVES) } ON
ROWS, { Descendants ([PopulationDate].[All PopulationDate].[" +
Parameters!ReportYear.Value + "], [PopulationDate].[Month], LEAVES)} ON PAGES
FROM PopulationActualAndSalesTarget"</CommandText>
<rd:UseGenericDesigner>true</rd:UseGenericDesigner>
</Query>
</DataSet>
</DataSets>
<LeftMargin>2.5cm</LeftMargin>
<rd:SnapToGrid>true</rd:SnapToGrid>
<PageHeight>29.7cm</PageHeight>
<rd:DrawGrid>true</rd:DrawGrid>
<PageWidth>21cm</PageWidth>
<rd:ReportID>d36619a3-0ff9-4f79-b9a9-52cd0865cb2c</rd:ReportID>
<BottomMargin>2.5cm</BottomMargin>
<ReportParameters>
<ReportParameter Name="ReportYear">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>Year</Prompt>
<ValidValues>
<ParameterValues>
<ParameterValue>
<Value>2004</Value>
</ParameterValue>
<ParameterValue>
<Value>2003</Value>
</ParameterValue>
<ParameterValue>
<Value>2002</Value>
</ParameterValue>
<ParameterValue>
<Value>2001</Value>
</ParameterValue>
</ParameterValues>
</ValidValues>
</ReportParameter>
<ReportParameter Name="ReportTeam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>Team</Prompt>
<ValidValues>
<ParameterValues>
<ParameterValue>
<Value>All Consultant</Value>
<Label>All Teams</Label>
</ParameterValue>
<ParameterValue>
<Value>Team 1</Value>
</ParameterValue>
<ParameterValue>
<Value>Team 2</Value>
</ParameterValue>
<ParameterValue>
<Value>Team 3</Value>
</ParameterValue>
<ParameterValue>
<Value>Team 4</Value>
</ParameterValue>
<ParameterValue>
<Value>Team 5</Value>
</ParameterValue>
</ParameterValues>
</ValidValues>
</ReportParameter>
</ReportParameters>
<Language>en-US</Language>
</Report>
Thanks.
Ben.
"Yoshi" wrote:
> Can you post some code?
> Dave
> "Ben Mann" <BenMann@.discussions.microsoft.com> wrote in message
> news:976C1E52-2D9F-4EA3-AC3E-1D7440B8FAB3@.microsoft.com...
> > Hello,
> >
> > I am trying to export some reports to excel format, using Reporting
> > Services
> > SP1. It contains an OLAP query and a matrix allowing drill-down.
> >
> > Reporting services errors with:
> > Exception of type
> > Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
> > thrown. (rrRenderingError) Get Online Help
> > Exception of type
> > Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
> > thrown.
> > Object reference not set to an instance of an object.
> >
> > An anyone help?
> >
> > Thanks.
> >
> > Ben.
>
>sql

excel export problem

Hi all,
We have a big report with 4 or 5 levels of drill downs and various other
expressions.
While exporting to excel format, unlike other formats, the drill down
capability and other expressions as formulas are also exported. Thus if the
report that is exported is large then exporting does not succeed and excel
throws an error.
"Damage to the file was so extensive that repairs were not possible. Excel
attempted to recover your formulas and values, but some data may have been
lost or corrupted."
I am using sql server 2005 reporting services sp1. I think this was common
problem and it seems it is not yet fixed. Also I see the answer to this
question as exporting to csv format with ASCII encoding. However, we cannot
use this trick. My question is, is there a way (something like device
information setting or any other property that exists in reporting services)
to prevent drill down information and formulas from reaching excel. however
the font/background color, heading and other stuff, as they appear in pdf
format, should also appear in excel?
is this possible?
Please reply as early as possible.
thanks.Hi,
Formulas can be omitted with "rc:OmitFormulas=True" in the URL. May be you
can use two URL's one with HTML's and the other with Excel as format and
omitting formula's and removing "Action" from the second report so when you
save in excel it removes hyperlink and formulas.
Let me know how you are intend to display from report manager or your
customized code. In the second option we can do it using two URL's.
Amarnath
"msdnuser" wrote:
> Hi all,
> We have a big report with 4 or 5 levels of drill downs and various other
> expressions.
> While exporting to excel format, unlike other formats, the drill down
> capability and other expressions as formulas are also exported. Thus if the
> report that is exported is large then exporting does not succeed and excel
> throws an error.
> "Damage to the file was so extensive that repairs were not possible. Excel
> attempted to recover your formulas and values, but some data may have been
> lost or corrupted."
> I am using sql server 2005 reporting services sp1. I think this was common
> problem and it seems it is not yet fixed. Also I see the answer to this
> question as exporting to csv format with ASCII encoding. However, we cannot
> use this trick. My question is, is there a way (something like device
> information setting or any other property that exists in reporting services)
> to prevent drill down information and formulas from reaching excel. however
> the font/background color, heading and other stuff, as they appear in pdf
> format, should also appear in excel?
> is this possible?
> Please reply as early as possible.
> thanks.|||Hi,
Thank you for the reply. Can you tell me how to remove actions for excel
export.
We are using custom webapplication to display the reports.
I tried to render the report in excel format using "url acess" method
applying rc:omitFormula=true. Still I got the same error message. Is there a
way to stop the drill down information from reaching excel? does removing
actions will help this drill down issue too?
Thanks.
"Amarnath" wrote:
> Hi,
> Formulas can be omitted with "rc:OmitFormulas=True" in the URL. May be you
> can use two URL's one with HTML's and the other with Excel as format and
> omitting formula's and removing "Action" from the second report so when you
> save in excel it removes hyperlink and formulas.
> Let me know how you are intend to display from report manager or your
> customized code. In the second option we can do it using two URL's.
> Amarnath
>
> "msdnuser" wrote:
> > Hi all,
> >
> > We have a big report with 4 or 5 levels of drill downs and various other
> > expressions.
> > While exporting to excel format, unlike other formats, the drill down
> > capability and other expressions as formulas are also exported. Thus if the
> > report that is exported is large then exporting does not succeed and excel
> > throws an error.
> >
> > "Damage to the file was so extensive that repairs were not possible. Excel
> > attempted to recover your formulas and values, but some data may have been
> > lost or corrupted."
> >
> > I am using sql server 2005 reporting services sp1. I think this was common
> > problem and it seems it is not yet fixed. Also I see the answer to this
> > question as exporting to csv format with ASCII encoding. However, we cannot
> > use this trick. My question is, is there a way (something like device
> > information setting or any other property that exists in reporting services)
> > to prevent drill down information and formulas from reaching excel. however
> > the font/background color, heading and other stuff, as they appear in pdf
> > format, should also appear in excel?
> > is this possible?
> >
> > Please reply as early as possible.
> >
> > thanks.|||Hi,
If you are using custom there you can do it.
Create a copy of your original report and keep everything same except all
hyperlinks,
e.g report1.RDL, Report_1.RDL.
You can create a hyperlink something like "Export to Excel" when the users
click the link it will be directed to the "copy of the report which you
removed links (Report_1.RDL)"
You should be able to do it with a little bit of coding.
Amarnath
"msdnuser" wrote:
> Hi,
> Thank you for the reply. Can you tell me how to remove actions for excel
> export.
> We are using custom webapplication to display the reports.
> I tried to render the report in excel format using "url acess" method
> applying rc:omitFormula=true. Still I got the same error message. Is there a
> way to stop the drill down information from reaching excel? does removing
> actions will help this drill down issue too?
> Thanks.
> "Amarnath" wrote:
> > Hi,
> > Formulas can be omitted with "rc:OmitFormulas=True" in the URL. May be you
> > can use two URL's one with HTML's and the other with Excel as format and
> > omitting formula's and removing "Action" from the second report so when you
> > save in excel it removes hyperlink and formulas.
> >
> > Let me know how you are intend to display from report manager or your
> > customized code. In the second option we can do it using two URL's.
> >
> > Amarnath
> >
> >
> > "msdnuser" wrote:
> >
> > > Hi all,
> > >
> > > We have a big report with 4 or 5 levels of drill downs and various other
> > > expressions.
> > > While exporting to excel format, unlike other formats, the drill down
> > > capability and other expressions as formulas are also exported. Thus if the
> > > report that is exported is large then exporting does not succeed and excel
> > > throws an error.
> > >
> > > "Damage to the file was so extensive that repairs were not possible. Excel
> > > attempted to recover your formulas and values, but some data may have been
> > > lost or corrupted."
> > >
> > > I am using sql server 2005 reporting services sp1. I think this was common
> > > problem and it seems it is not yet fixed. Also I see the answer to this
> > > question as exporting to csv format with ASCII encoding. However, we cannot
> > > use this trick. My question is, is there a way (something like device
> > > information setting or any other property that exists in reporting services)
> > > to prevent drill down information and formulas from reaching excel. however
> > > the font/background color, heading and other stuff, as they appear in pdf
> > > format, should also appear in excel?
> > > is this possible?
> > >
> > > Please reply as early as possible.
> > >
> > > thanks.|||Hi ringt,
Thank you for your post and thanks Amarnath's solution.
I would like to know whether the solution from Amarnath is helpful. If the
solution is not match your scenario or you still have further questions or
concern, would you please send the RDL file and the datasource to me? I
understand the information may be sensitive to you, my direct email address
is weilu@.ONLINE.microsoft.com ( Please remove the ONLINE. when you send the
email), you may send the file to me directly and I will keep secure.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Amarnath and Wei Lu,
The solution that Amarnath has given will make the excel export always
expanded. But what we want is something similar to PDF export.
Initially the report will be all collapsed and the user will see this report
in our web application in HTML format. Then user might expand one or two
nodes to any level that he likes. Then user might export to several formats,
one among them is excel.
If he export to excel, then whatever he saw in HTML page before clicking
excel export button should be available/visible in excel report. But there
should not be drilldowns in excel report. Thus only those rows that he saw in
HTML should actually go to Excel like PDF exporting.
Is this possible some how'
Thanks.
"Wei Lu" wrote:
> Hi ringt,
> Thank you for your post and thanks Amarnath's solution.
> I would like to know whether the solution from Amarnath is helpful. If the
> solution is not match your scenario or you still have further questions or
> concern, would you please send the RDL file and the datasource to me? I
> understand the information may be sensitive to you, my direct email address
> is weilu@.ONLINE.microsoft.com ( Please remove the ONLINE. when you send the
> email), you may send the file to me directly and I will keep secure.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi ringt,
Thanks for the update.
I tested on my side and it just works fine. The report is all collapsed and
I expand some node and then export to Excel. It just works as your request
on my side on both SQL Server Reporting Services 2005 and 2000.
Would you please send the rdl file to me for further troubleshoot?
I understand the information may be sensitive to you, my direct email
address is weilu@.ONLINE.microsoft.com (Please remove the ONLINE. when you
send the mail), you may send the file to me directly and I will keep secure.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi,
What you would have tried is normal export to excel. If your report has
drill down and if you expand one or two nodes and export to excel , it is
working good. But what I am saying is it should work the same way but further
expand collapse feature of drill down should not be available in excel export
like PDF. is this possible?
Thanks.
"Wei Lu" wrote:
> Hi ringt,
> Thanks for the update.
> I tested on my side and it just works fine. The report is all collapsed and
> I expand some node and then export to Excel. It just works as your request
> on my side on both SQL Server Reporting Services 2005 and 2000.
> Would you please send the rdl file to me for further troubleshoot?
> I understand the information may be sensitive to you, my direct email
> address is weilu@.ONLINE.microsoft.com (Please remove the ONLINE. when you
> send the mail), you may send the file to me directly and I will keep secure.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi ringt,
Thank you for the update.
I don't think it is possible to excel render works like pdf render since
PDF can not support any operation like expand collapse but excel did
support this operation.
The Excel render will export the collapse and the only thing you could do
is to write a custom render and use this to export your report.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||I dont think this can be done. Still its a funny idea, to take "Print screen"
as an image file. "It is as good as what you see is what you get" whether it
is possible you will have to check.
Amarnath.
"Wei Lu" wrote:
> Hi ringt,
> Thank you for the update.
> I don't think it is possible to excel render works like pdf render since
> PDF can not support any operation like expand collapse but excel did
> support this operation.
> The Excel render will export the collapse and the only thing you could do
> is to write a custom render and use this to export your report.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Thank you both for helping me by sharing your knowledge.
"Amarnath" wrote:
> I dont think this can be done. Still its a funny idea, to take "Print screen"
> as an image file. "It is as good as what you see is what you get" whether it
> is possible you will have to check.
> Amarnath.
> "Wei Lu" wrote:
> > Hi ringt,
> >
> > Thank you for the update.
> >
> > I don't think it is possible to excel render works like pdf render since
> > PDF can not support any operation like expand collapse but excel did
> > support this operation.
> >
> > The Excel render will export the collapse and the only thing you could do
> > is to write a custom render and use this to export your report.
> >
> > Sincerely,
> >
> > Wei Lu
> > Microsoft Online Community Support
> >
> > ==================================================> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> >
> > ==================================================> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >|||Hi ringt,
Thank you for the update.
If you have any questions or concerns, please feel free to let me know.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Excel export problem

Hi,
When you want to use the Excel export function, you may never get the export
even if it is less than 64K rows.
I suspect that the xml format of the generated file is so large that the
client computer runs out of memory.
For a 64K rows export, the xml is probably 64M rows?
Any Excel binary export format in sight?
Thanks
PhilippeSP1 (released today) supports native Excel format export.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Philippe Cand" <please_reply_only@.NG.com> wrote in message
news:uzm7QyOWEHA.2196@.TK2MSFTNGP10.phx.gbl...
> Hi,
> When you want to use the Excel export function, you may never get the
> export
> even if it is less than 64K rows.
> I suspect that the xml format of the generated file is so large that the
> client computer runs out of memory.
> For a 64K rows export, the xml is probably 64M rows?
> Any Excel binary export format in sight?
> Thanks
> Philippe
>

excel export not showing client name in heading

I am putting the client name in my header using ReportItems! reference to
textbox in report - this renders correctly on my server and in pdf however in
excel the client name is not showing up on the report. There are 2 textboxes
overlapping each other because I have 2 groups and when the page spans the
client name will come from the alt text box. I have tried NOT overlapping
them and the result is the same - neither one displays on the export to excel.This is common. In RS 2000, the pdf rendering extension didn't do it...
What you have to do to work around it is use rectangles and textboxes to
simulate a page header OR you can pass it in as a parameter.
-Tim
"MJT" <MJT@.discussions.microsoft.com> wrote in message
news:365BECF1-AD51-42E0-BF79-DE9011DC166C@.microsoft.com...
>I am putting the client name in my header using ReportItems! reference to
> textbox in report - this renders correctly on my server and in pdf however
> in
> excel the client name is not showing up on the report. There are 2
> textboxes
> overlapping each other because I have 2 groups and when the page spans the
> client name will come from the alt text box. I have tried NOT overlapping
> them and the result is the same - neither one displays on the export to
> excel.|||Thanks Tim,
Cant pass as a parm as they use client code (not the same) for the parm
and takes too long to run if I make it a report parm (since it cant be a
query parm I am using a stored procedure). I noticed your post about putting
this info not in a page heading but in a rectangle and hiding/showing which
might be an option if hiding/showing didnt leave white space when hidden (big
problem). Seems like such a simple basic thing that should work, doesnt it?
I mean ... who *doesnt* need data information in their heading'
"Tim Dot NoSpam" wrote:
> This is common. In RS 2000, the pdf rendering extension didn't do it...
> What you have to do to work around it is use rectangles and textboxes to
> simulate a page header OR you can pass it in as a parameter.
> -Tim
> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> news:365BECF1-AD51-42E0-BF79-DE9011DC166C@.microsoft.com...
> >I am putting the client name in my header using ReportItems! reference to
> > textbox in report - this renders correctly on my server and in pdf however
> > in
> > excel the client name is not showing up on the report. There are 2
> > textboxes
> > overlapping each other because I have 2 groups and when the page spans the
> > client name will come from the alt text box. I have tried NOT overlapping
> > them and the result is the same - neither one displays on the export to
> > excel.
>
>|||Hi
Can to tell me to Hide or disable page Header while exporting to Excel format.
calvin
"MJT" wrote:
> I am putting the client name in my header using ReportItems! reference to
> textbox in report - this renders correctly on my server and in pdf however in
> excel the client name is not showing up on the report. There are 2 textboxes
> overlapping each other because I have 2 groups and when the page spans the
> client name will come from the alt text box. I have tried NOT overlapping
> them and the result is the same - neither one displays on the export to excel.|||Hi
I want to export a report to excel format, but in excel the page header
should not come. Can u please help how to slove this.
Calvin
"Tim Dot NoSpam" wrote:
> This is common. In RS 2000, the pdf rendering extension didn't do it...
> What you have to do to work around it is use rectangles and textboxes to
> simulate a page header OR you can pass it in as a parameter.
> -Tim
> "MJT" <MJT@.discussions.microsoft.com> wrote in message
> news:365BECF1-AD51-42E0-BF79-DE9011DC166C@.microsoft.com...
> >I am putting the client name in my header using ReportItems! reference to
> > textbox in report - this renders correctly on my server and in pdf however
> > in
> > excel the client name is not showing up on the report. There are 2
> > textboxes
> > overlapping each other because I have 2 groups and when the page spans the
> > client name will come from the alt text box. I have tried NOT overlapping
> > them and the result is the same - neither one displays on the export to
> > excel.
>
>

Excel export missing table header

I am working with RS2000 SP2 and VS2003.

I have a simple report with just one table, two levels of grouping with subtotals and a table header. There is also a separate page header. The report renders correctly on screen and when printed.

When I export the report in Excel format the detail lines, group sub-totals and page head appear. However, the problem I have is that the table header is not shown. So the user can't make out what data is shown each column. How can I get the table header to appear when exporting to Excel?

TIA, Magendo_man

To complicate matters further, I have added another table to this report, which is a copy of the original one. This table uses the same dataset but is filtered and sorted differently, with no grouping and a footer total. I set the table to have a page break before it is printed.

Now when I export to Excel I get the same problem with missing table header for the first table, but I do get the table header for this second table.

TIA, Magendo_man

Excel Export Missing Rows - URGENT

Hello,
This question has been posted a few times and is DEFINITELY A SHOW STOPPER
for Reporting Services.
When exporting to Excel - the last row can turn up missing - Why is
Microsoft not responding to this?Unless you are part of managed newsgroups (MSDN subscriber) there is no
guarantee of a response from MS. Mostly peers answering questions (like me).
I suggest you open an incindent report. If it is a bug then I believe you
don't get charged but that is not my area of expertise (what MS charges and
doesn't charge for).
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"chanley54" <chanley54@.discussions.microsoft.com> wrote in message
news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> Hello,
> This question has been posted a few times and is DEFINITELY A SHOW STOPPER
> for Reporting Services.
> When exporting to Excel - the last row can turn up missing - Why is
> Microsoft not responding to this?
>|||This is correct. The best approach is to work through our product support
team. Otherwise, you can post it here but for us to repro, we would need
more than a general problem statement. It is best to isolate the problem as
small as possible and post an example repro using a known data set.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:e5eIIhY0EHA.356@.TK2MSFTNGP10.phx.gbl...
> Unless you are part of managed newsgroups (MSDN subscriber) there is no
> guarantee of a response from MS. Mostly peers answering questions (like
> me).
> I suggest you open an incindent report. If it is a bug then I believe you
> don't get charged but that is not my area of expertise (what MS charges
> and
> doesn't charge for).
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
>> Hello,
>> This question has been posted a few times and is DEFINITELY A SHOW
>> STOPPER
>> for Reporting Services.
>> When exporting to Excel - the last row can turn up missing - Why is
>> Microsoft not responding to this?
>|||Hopefully by now you found a work-around, but in case you did not, I found
that if I re-arrange the stuff above the table a bit, like headers and
other text, etc, it fixes the problem.
"chanley54" <chanley54@.discussions.microsoft.com> wrote in message
news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> Hello,
> This question has been posted a few times and is DEFINITELY A SHOW STOPPER
> for Reporting Services.
> When exporting to Excel - the last row can turn up missing - Why is
> Microsoft not responding to this?
>|||I suggest opening up a support case. If it is a bug you don't get charged.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> Hopefully by now you found a work-around, but in case you did not, I found
> that if I re-arrange the stuff above the table a bit, like headers and
> other text, etc, it fixes the problem.
> "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > Hello,
> >
> > This question has been posted a few times and is DEFINITELY A SHOW
STOPPER
> > for Reporting Services.
> >
> > When exporting to Excel - the last row can turn up missing - Why is
> > Microsoft not responding to this?
> >
>|||The problem is very easy to reproduce. I don't see why one of us has to open
a support case in the hopes of not getting charged.
I don't see why MS cannot run a few tests as I am sure they will see the
problem that multiple developers are complaining about.
If MS needs a sample report and dataset I will be happy to provide.
Regards.
"Bruce L-C [MVP]" wrote:
> I suggest opening up a support case. If it is a bug you don't get charged.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > Hopefully by now you found a work-around, but in case you did not, I found
> > that if I re-arrange the stuff above the table a bit, like headers and
> > other text, etc, it fixes the problem.
> >
> > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > Hello,
> > >
> > > This question has been posted a few times and is DEFINITELY A SHOW
> STOPPER
> > > for Reporting Services.
> > >
> > > When exporting to Excel - the last row can turn up missing - Why is
> > > Microsoft not responding to this?
> > >
> >
> >
>
>|||If opening a support case would have fixed the problem this month, then it
might have been worth the effort.
I posted this problem just after the release of SP1 (without SP1 one cannot
export to Excel 2000), many others posted it since then, and even if I filed
an incident then, there is no such thing as SP2 yet, and the client would
have been off the roof by now.
What I don't understand is why the MS guys don't just admit that it is a
problem and suggest a work-around or release a hot-fix or something. As I
said, I found sizing the stuff above the table like headers, other text,
etc, fixes the problem (haven't had any complaints from the client), and the
report that looses the last row, attached to my other posting, was fixed
like this and is running at the client.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> I suggest opening up a support case. If it is a bug you don't get charged.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > Hopefully by now you found a work-around, but in case you did not, I
found
> > that if I re-arrange the stuff above the table a bit, like headers and
> > other text, etc, it fixes the problem.
> >
> > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > Hello,
> > >
> > > This question has been posted a few times and is DEFINITELY A SHOW
> STOPPER
> > > for Reporting Services.
> > >
> > > When exporting to Excel - the last row can turn up missing - Why is
> > > Microsoft not responding to this?
> > >
> >
> >
>|||I just changed my view to see all messages and I then see that this is a
continuation of a posting from awhile back.
It sounds like
1. you have a work around.
2. you want support from this newsgroup for your problem
3. you don't want to submit a support incident
So, however much you feel like #2 should be happening for you, that isn't
how the newsgroup is setup to operate. You either need to open an incident
or have an msdn subscription. The only people that get any support other
than peer support is if you are an MSDN subscription holder in which case
you this newsgroup is part of the managed newsgroups.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> If opening a support case would have fixed the problem this month, then it
> might have been worth the effort.
> I posted this problem just after the release of SP1 (without SP1 one
cannot
> export to Excel 2000), many others posted it since then, and even if I
filed
> an incident then, there is no such thing as SP2 yet, and the client would
> have been off the roof by now.
> What I don't understand is why the MS guys don't just admit that it is a
> problem and suggest a work-around or release a hot-fix or something. As I
> said, I found sizing the stuff above the table like headers, other text,
> etc, fixes the problem (haven't had any complaints from the client), and
the
> report that looses the last row, attached to my other posting, was fixed
> like this and is running at the client.
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > I suggest opening up a support case. If it is a bug you don't get
charged.
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > > Hopefully by now you found a work-around, but in case you did not, I
> found
> > > that if I re-arrange the stuff above the table a bit, like headers
and
> > > other text, etc, it fixes the problem.
> > >
> > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > > Hello,
> > > >
> > > > This question has been posted a few times and is DEFINITELY A SHOW
> > STOPPER
> > > > for Reporting Services.
> > > >
> > > > When exporting to Excel - the last row can turn up missing - Why is
> > > > Microsoft not responding to this?
> > > >
> > >
> > >
> >
> >
>|||Read the whole thread, Brian Welcker said "you can post it here but for us
to repro, we would need more than a general problem statement" etc. This is
exactly what I did way back (I found my old file and posted it again). The
same issue crops up, actually frequently, and an MS employee does not say
it's a bug, don't they know yet, or do they only tell people that contact
the product support team?
Our company has a universal MSDN subscription, and I am not hunting this
issue, I bumped into the thread by accident, but could not keep quiet -
something walks and quacks like a duck.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> I just changed my view to see all messages and I then see that this is a
> continuation of a posting from awhile back.
> It sounds like
> 1. you have a work around.
> 2. you want support from this newsgroup for your problem
> 3. you don't want to submit a support incident
> So, however much you feel like #2 should be happening for you, that isn't
> how the newsgroup is setup to operate. You either need to open an incident
> or have an msdn subscription. The only people that get any support other
> than peer support is if you are an MSDN subscription holder in which case
> you this newsgroup is part of the managed newsgroups.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> > If opening a support case would have fixed the problem this month, then
it
> > might have been worth the effort.
> > I posted this problem just after the release of SP1 (without SP1 one
> cannot
> > export to Excel 2000), many others posted it since then, and even if I
> filed
> > an incident then, there is no such thing as SP2 yet, and the client
would
> > have been off the roof by now.
> > What I don't understand is why the MS guys don't just admit that it is a
> > problem and suggest a work-around or release a hot-fix or something. As
I
> > said, I found sizing the stuff above the table like headers, other text,
> > etc, fixes the problem (haven't had any complaints from the client), and
> the
> > report that looses the last row, attached to my other posting, was fixed
> > like this and is running at the client.
> >
> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > > I suggest opening up a support case. If it is a bug you don't get
> charged.
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > > > Hopefully by now you found a work-around, but in case you did not, I
> > found
> > > > that if I re-arrange the stuff above the table a bit, like headers
> and
> > > > other text, etc, it fixes the problem.
> > > >
> > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > > > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > > > Hello,
> > > > >
> > > > > This question has been posted a few times and is DEFINITELY A SHOW
> > > STOPPER
> > > > > for Reporting Services.
> > > > >
> > > > > When exporting to Excel - the last row can turn up missing - Why
is
> > > > > Microsoft not responding to this?
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||If you have universal you need to just post via a managed newsgroup (if you
haven't done this you post with a special fake email address that you have
registered in MSDN website and then someone from MS will answer and take
your repro case.
I still think you have a misconception about this newsgroup, that someone
from MS is watching every thread and that there should be some sort of
official statement from them. That is not how it works. If Brian happens to
stop by then he might do something with it. I noticed that he first said the
best thing was to get product support involved and then he mentions posting.
So he went both ways with his answer. Posting might get a response, with
managed newsgroup or product support you will get a response. Otherwise it
is peer.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> Read the whole thread, Brian Welcker said "you can post it here but for
us
> to repro, we would need more than a general problem statement" etc. This
is
> exactly what I did way back (I found my old file and posted it again). The
> same issue crops up, actually frequently, and an MS employee does not say
> it's a bug, don't they know yet, or do they only tell people that contact
> the product support team?
> Our company has a universal MSDN subscription, and I am not hunting this
> issue, I bumped into the thread by accident, but could not keep quiet -
> something walks and quacks like a duck.
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> > I just changed my view to see all messages and I then see that this is a
> > continuation of a posting from awhile back.
> >
> > It sounds like
> > 1. you have a work around.
> > 2. you want support from this newsgroup for your problem
> > 3. you don't want to submit a support incident
> >
> > So, however much you feel like #2 should be happening for you, that
isn't
> > how the newsgroup is setup to operate. You either need to open an
incident
> > or have an msdn subscription. The only people that get any support other
> > than peer support is if you are an MSDN subscription holder in which
case
> > you this newsgroup is part of the managed newsgroups.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> >
> >
> > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> > > If opening a support case would have fixed the problem this month,
then
> it
> > > might have been worth the effort.
> > > I posted this problem just after the release of SP1 (without SP1 one
> > cannot
> > > export to Excel 2000), many others posted it since then, and even if I
> > filed
> > > an incident then, there is no such thing as SP2 yet, and the client
> would
> > > have been off the roof by now.
> > > What I don't understand is why the MS guys don't just admit that it is
a
> > > problem and suggest a work-around or release a hot-fix or something.
As
> I
> > > said, I found sizing the stuff above the table like headers, other
text,
> > > etc, fixes the problem (haven't had any complaints from the client),
and
> > the
> > > report that looses the last row, attached to my other posting, was
fixed
> > > like this and is running at the client.
> > >
> > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > > > I suggest opening up a support case. If it is a bug you don't get
> > charged.
> > > >
> > > > --
> > > > Bruce Loehle-Conger
> > > > MVP SQL Server Reporting Services
> > > >
> > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > > > > Hopefully by now you found a work-around, but in case you did not,
I
> > > found
> > > > > that if I re-arrange the stuff above the table a bit, like
headers
> > and
> > > > > other text, etc, it fixes the problem.
> > > > >
> > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > > > > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > > > > Hello,
> > > > > >
> > > > > > This question has been posted a few times and is DEFINITELY A
SHOW
> > > > STOPPER
> > > > > > for Reporting Services.
> > > > > >
> > > > > > When exporting to Excel - the last row can turn up missing - Why
> is
> > > > > > Microsoft not responding to this?
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>|||I am posting this through the "Managed NewsGroup"
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
and am still not getting an answer. I also have an MSDN subscription.
Based upon the above postings - shouldn't I get a response back?
The workaround will not work for me as we have almost a 1,000 reports that
get exported to Excel. Yes - we only notced this after SP1.
It is obvious that this is a bug (a pretty big one at that). I don't want
to get into a "p*ss*ng contest" about this but am tired of the back and forth
about submitting a report case. It is simply a bug that is relatively simple
to reproduce.
"Bruce L-C [MVP]" wrote:
> If you have universal you need to just post via a managed newsgroup (if you
> haven't done this you post with a special fake email address that you have
> registered in MSDN website and then someone from MS will answer and take
> your repro case.
> I still think you have a misconception about this newsgroup, that someone
> from MS is watching every thread and that there should be some sort of
> official statement from them. That is not how it works. If Brian happens to
> stop by then he might do something with it. I noticed that he first said the
> best thing was to get product support involved and then he mentions posting.
> So he went both ways with his answer. Posting might get a response, with
> managed newsgroup or product support you will get a response. Otherwise it
> is peer.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> > Read the whole thread, Brian Welcker said "you can post it here but for
> us
> > to repro, we would need more than a general problem statement" etc. This
> is
> > exactly what I did way back (I found my old file and posted it again). The
> > same issue crops up, actually frequently, and an MS employee does not say
> > it's a bug, don't they know yet, or do they only tell people that contact
> > the product support team?
> >
> > Our company has a universal MSDN subscription, and I am not hunting this
> > issue, I bumped into the thread by accident, but could not keep quiet -
> > something walks and quacks like a duck.
> >
> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> > > I just changed my view to see all messages and I then see that this is a
> > > continuation of a posting from awhile back.
> > >
> > > It sounds like
> > > 1. you have a work around.
> > > 2. you want support from this newsgroup for your problem
> > > 3. you don't want to submit a support incident
> > >
> > > So, however much you feel like #2 should be happening for you, that
> isn't
> > > how the newsgroup is setup to operate. You either need to open an
> incident
> > > or have an msdn subscription. The only people that get any support other
> > > than peer support is if you are an MSDN subscription holder in which
> case
> > > you this newsgroup is part of the managed newsgroups.
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > >
> > >
> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> > > > If opening a support case would have fixed the problem this month,
> then
> > it
> > > > might have been worth the effort.
> > > > I posted this problem just after the release of SP1 (without SP1 one
> > > cannot
> > > > export to Excel 2000), many others posted it since then, and even if I
> > > filed
> > > > an incident then, there is no such thing as SP2 yet, and the client
> > would
> > > > have been off the roof by now.
> > > > What I don't understand is why the MS guys don't just admit that it is
> a
> > > > problem and suggest a work-around or release a hot-fix or something.
> As
> > I
> > > > said, I found sizing the stuff above the table like headers, other
> text,
> > > > etc, fixes the problem (haven't had any complaints from the client),
> and
> > > the
> > > > report that looses the last row, attached to my other posting, was
> fixed
> > > > like this and is running at the client.
> > > >
> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > > > > I suggest opening up a support case. If it is a bug you don't get
> > > charged.
> > > > >
> > > > > --
> > > > > Bruce Loehle-Conger
> > > > > MVP SQL Server Reporting Services
> > > > >
> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > > > > > Hopefully by now you found a work-around, but in case you did not,
> I
> > > > found
> > > > > > that if I re-arrange the stuff above the table a bit, like
> headers
> > > and
> > > > > > other text, etc, it fixes the problem.
> > > > > >
> > > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > > > > > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > > > > > Hello,
> > > > > > >
> > > > > > > This question has been posted a few times and is DEFINITELY A
> SHOW
> > > > > STOPPER
> > > > > > > for Reporting Services.
> > > > > > >
> > > > > > > When exporting to Excel - the last row can turn up missing - Why
> > is
> > > > > > > Microsoft not responding to this?
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>|||I am trying to help you. Remember before attacking me that I help people
just for the hell of it. As such I am trying to let you know how things work
so you can successfully get your issue resolved.
About managed newsgroups. There is no difference between this newsgroup and
a managed newsgroup. They are the same thing (whether you use a web
interface or a outlook express). To have your posting to be included under
the managed newsgroup support terms (I believe it is within 2 business days)
you have to do two things.
- you have to initiate the posting. The software they use to manage the
process only looks at whoever started the thread.
- the return email address has to be the fake one registered as part of the
managed newsgroup process. I'm not positive but looking at your email
address for your post it does not look to me like it is the fake one
registered with MS. If they do not see the one that has been registered with
them then it is ignored. Note that this is not the email address that the
MSDN subscription has for you (i.e. it is NOT the passport email address,
you have to specifically register an additional fake one that is
specifically for the managed newsgroup support).
Go here:
http://msdn.microsoft.com/newsgroups/managed/
Login with passport
Then scroll down to here:
Getting Started
The managed newsgroups are easy to use. Just follow these simple
instructions:
a.. Register by creating your unique no-spam alias
And click on the link.
I didn't find it real intuitive about how it operates (first posting, using
the alias)
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"chanley54" <chanley54@.discussions.microsoft.com> wrote in message
news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
>I am posting this through the "Managed NewsGroup"
> http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> and am still not getting an answer. I also have an MSDN subscription.
> Based upon the above postings - shouldn't I get a response back?
> The workaround will not work for me as we have almost a 1,000 reports that
> get exported to Excel. Yes - we only notced this after SP1.
> It is obvious that this is a bug (a pretty big one at that). I don't want
> to get into a "p*ss*ng contest" about this but am tired of the back and
> forth
> about submitting a report case. It is simply a bug that is relatively
> simple
> to reproduce.
>
> "Bruce L-C [MVP]" wrote:
>> If you have universal you need to just post via a managed newsgroup (if
>> you
>> haven't done this you post with a special fake email address that you
>> have
>> registered in MSDN website and then someone from MS will answer and take
>> your repro case.
>> I still think you have a misconception about this newsgroup, that someone
>> from MS is watching every thread and that there should be some sort of
>> official statement from them. That is not how it works. If Brian happens
>> to
>> stop by then he might do something with it. I noticed that he first said
>> the
>> best thing was to get product support involved and then he mentions
>> posting.
>> So he went both ways with his answer. Posting might get a response, with
>> managed newsgroup or product support you will get a response. Otherwise
>> it
>> is peer.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
>> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
>> > Read the whole thread, Brian Welcker said "you can post it here but
>> > for
>> us
>> > to repro, we would need more than a general problem statement" etc.
>> > This
>> is
>> > exactly what I did way back (I found my old file and posted it again).
>> > The
>> > same issue crops up, actually frequently, and an MS employee does not
>> > say
>> > it's a bug, don't they know yet, or do they only tell people that
>> > contact
>> > the product support team?
>> >
>> > Our company has a universal MSDN subscription, and I am not hunting
>> > this
>> > issue, I bumped into the thread by accident, but could not keep quiet -
>> > something walks and quacks like a duck.
>> >
>> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
>> > > I just changed my view to see all messages and I then see that this
>> > > is a
>> > > continuation of a posting from awhile back.
>> > >
>> > > It sounds like
>> > > 1. you have a work around.
>> > > 2. you want support from this newsgroup for your problem
>> > > 3. you don't want to submit a support incident
>> > >
>> > > So, however much you feel like #2 should be happening for you, that
>> isn't
>> > > how the newsgroup is setup to operate. You either need to open an
>> incident
>> > > or have an msdn subscription. The only people that get any support
>> > > other
>> > > than peer support is if you are an MSDN subscription holder in which
>> case
>> > > you this newsgroup is part of the managed newsgroups.
>> > >
>> > >
>> > > --
>> > > Bruce Loehle-Conger
>> > > MVP SQL Server Reporting Services
>> > >
>> > >
>> > >
>> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
>> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
>> > > > If opening a support case would have fixed the problem this month,
>> then
>> > it
>> > > > might have been worth the effort.
>> > > > I posted this problem just after the release of SP1 (without SP1
>> > > > one
>> > > cannot
>> > > > export to Excel 2000), many others posted it since then, and even
>> > > > if I
>> > > filed
>> > > > an incident then, there is no such thing as SP2 yet, and the client
>> > would
>> > > > have been off the roof by now.
>> > > > What I don't understand is why the MS guys don't just admit that it
>> > > > is
>> a
>> > > > problem and suggest a work-around or release a hot-fix or
>> > > > something.
>> As
>> > I
>> > > > said, I found sizing the stuff above the table like headers, other
>> text,
>> > > > etc, fixes the problem (haven't had any complaints from the
>> > > > client),
>> and
>> > > the
>> > > > report that looses the last row, attached to my other posting, was
>> fixed
>> > > > like this and is running at the client.
>> > > >
>> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
>> > > > > I suggest opening up a support case. If it is a bug you don't get
>> > > charged.
>> > > > >
>> > > > > --
>> > > > > Bruce Loehle-Conger
>> > > > > MVP SQL Server Reporting Services
>> > > > >
>> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
>> > > > > message
>> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
>> > > > > > Hopefully by now you found a work-around, but in case you did
>> > > > > > not,
>> I
>> > > > found
>> > > > > > that if I re-arrange the stuff above the table a bit, like
>> headers
>> > > and
>> > > > > > other text, etc, it fixes the problem.
>> > > > > >
>> > > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in
>> > > > > > message
>> > > > > > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
>> > > > > > > Hello,
>> > > > > > >
>> > > > > > > This question has been posted a few times and is DEFINITELY A
>> SHOW
>> > > > > STOPPER
>> > > > > > > for Reporting Services.
>> > > > > > >
>> > > > > > > When exporting to Excel - the last row can turn up missing -
>> > > > > > > Why
>> > is
>> > > > > > > Microsoft not responding to this?
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > >
>> > >
>> >
>> >
>>|||Bruce,
That's exactly what I have been doing. We do appricate the help. This
posting was made through the same process that you described.
Perhaps I am doing something wrong but my return address shows the following:
"chanley54@.discussions.microsoft.com"
Regards.
"Bruce L-C [MVP]" wrote:
> I am trying to help you. Remember before attacking me that I help people
> just for the hell of it. As such I am trying to let you know how things work
> so you can successfully get your issue resolved.
> About managed newsgroups. There is no difference between this newsgroup and
> a managed newsgroup. They are the same thing (whether you use a web
> interface or a outlook express). To have your posting to be included under
> the managed newsgroup support terms (I believe it is within 2 business days)
> you have to do two things.
> - you have to initiate the posting. The software they use to manage the
> process only looks at whoever started the thread.
> - the return email address has to be the fake one registered as part of the
> managed newsgroup process. I'm not positive but looking at your email
> address for your post it does not look to me like it is the fake one
> registered with MS. If they do not see the one that has been registered with
> them then it is ignored. Note that this is not the email address that the
> MSDN subscription has for you (i.e. it is NOT the passport email address,
> you have to specifically register an additional fake one that is
> specifically for the managed newsgroup support).
> Go here:
> http://msdn.microsoft.com/newsgroups/managed/
> Login with passport
> Then scroll down to here:
> Getting Started
> The managed newsgroups are easy to use. Just follow these simple
> instructions:
> a.. Register by creating your unique no-spam alias
> And click on the link.
> I didn't find it real intuitive about how it operates (first posting, using
> the alias)
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
> >I am posting this through the "Managed NewsGroup"
> > http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> >
> > and am still not getting an answer. I also have an MSDN subscription.
> > Based upon the above postings - shouldn't I get a response back?
> >
> > The workaround will not work for me as we have almost a 1,000 reports that
> > get exported to Excel. Yes - we only notced this after SP1.
> >
> > It is obvious that this is a bug (a pretty big one at that). I don't want
> > to get into a "p*ss*ng contest" about this but am tired of the back and
> > forth
> > about submitting a report case. It is simply a bug that is relatively
> > simple
> > to reproduce.
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> If you have universal you need to just post via a managed newsgroup (if
> >> you
> >> haven't done this you post with a special fake email address that you
> >> have
> >> registered in MSDN website and then someone from MS will answer and take
> >> your repro case.
> >>
> >> I still think you have a misconception about this newsgroup, that someone
> >> from MS is watching every thread and that there should be some sort of
> >> official statement from them. That is not how it works. If Brian happens
> >> to
> >> stop by then he might do something with it. I noticed that he first said
> >> the
> >> best thing was to get product support involved and then he mentions
> >> posting.
> >> So he went both ways with his answer. Posting might get a response, with
> >> managed newsgroup or product support you will get a response. Otherwise
> >> it
> >> is peer.
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> >> > Read the whole thread, Brian Welcker said "you can post it here but
> >> > for
> >> us
> >> > to repro, we would need more than a general problem statement" etc.
> >> > This
> >> is
> >> > exactly what I did way back (I found my old file and posted it again).
> >> > The
> >> > same issue crops up, actually frequently, and an MS employee does not
> >> > say
> >> > it's a bug, don't they know yet, or do they only tell people that
> >> > contact
> >> > the product support team?
> >> >
> >> > Our company has a universal MSDN subscription, and I am not hunting
> >> > this
> >> > issue, I bumped into the thread by accident, but could not keep quiet -
> >> > something walks and quacks like a duck.
> >> >
> >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> >> > > I just changed my view to see all messages and I then see that this
> >> > > is a
> >> > > continuation of a posting from awhile back.
> >> > >
> >> > > It sounds like
> >> > > 1. you have a work around.
> >> > > 2. you want support from this newsgroup for your problem
> >> > > 3. you don't want to submit a support incident
> >> > >
> >> > > So, however much you feel like #2 should be happening for you, that
> >> isn't
> >> > > how the newsgroup is setup to operate. You either need to open an
> >> incident
> >> > > or have an msdn subscription. The only people that get any support
> >> > > other
> >> > > than peer support is if you are an MSDN subscription holder in which
> >> case
> >> > > you this newsgroup is part of the managed newsgroups.
> >> > >
> >> > >
> >> > > --
> >> > > Bruce Loehle-Conger
> >> > > MVP SQL Server Reporting Services
> >> > >
> >> > >
> >> > >
> >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> >> > > > If opening a support case would have fixed the problem this month,
> >> then
> >> > it
> >> > > > might have been worth the effort.
> >> > > > I posted this problem just after the release of SP1 (without SP1
> >> > > > one
> >> > > cannot
> >> > > > export to Excel 2000), many others posted it since then, and even
> >> > > > if I
> >> > > filed
> >> > > > an incident then, there is no such thing as SP2 yet, and the client
> >> > would
> >> > > > have been off the roof by now.
> >> > > > What I don't understand is why the MS guys don't just admit that it
> >> > > > is
> >> a
> >> > > > problem and suggest a work-around or release a hot-fix or
> >> > > > something.
> >> As
> >> > I
> >> > > > said, I found sizing the stuff above the table like headers, other
> >> text,
> >> > > > etc, fixes the problem (haven't had any complaints from the
> >> > > > client),
> >> and
> >> > > the
> >> > > > report that looses the last row, attached to my other posting, was
> >> fixed
> >> > > > like this and is running at the client.
> >> > > >
> >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> >> > > > > I suggest opening up a support case. If it is a bug you don't get
> >> > > charged.
> >> > > > >
> >> > > > > --
> >> > > > > Bruce Loehle-Conger
> >> > > > > MVP SQL Server Reporting Services
> >> > > > >
> >> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> >> > > > > message
> >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> >> > > > > > Hopefully by now you found a work-around, but in case you did
> >> > > > > > not,
> >> I
> >> > > > found
> >> > > > > > that if I re-arrange the stuff above the table a bit, like
> >> headers
> >> > > and
> >> > > > > > other text, etc, it fixes the problem.
> >> > > > > >
> >> > > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in
> >> > > > > > message
> >> > > > > > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> >> > > > > > > Hello,
> >> > > > > > >
> >> > > > > > > This question has been posted a few times and is DEFINITELY A
> >> SHOW
> >> > > > > STOPPER
> >> > > > > > > for Reporting Services.
> >> > > > > > >
> >> > > > > > > When exporting to Excel - the last row can turn up missing -
> >> > > > > > > Why
> >> > is
> >> > > > > > > Microsoft not responding to this?
> >> > > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >>
>
>|||Bruce,
Correction - I changed my alias and searched through the Managed NewsGroup
section and it brought me to the following:
http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
Again - MS says that we will have a response in two day. Sorry to beat this
to death.
"chanley54" wrote:
> Bruce,
> That's exactly what I have been doing. We do appricate the help. This
> posting was made through the same process that you described.
> Perhaps I am doing something wrong but my return address shows the following:
> "chanley54@.discussions.microsoft.com"
> Regards.
>
> "Bruce L-C [MVP]" wrote:
> > I am trying to help you. Remember before attacking me that I help people
> > just for the hell of it. As such I am trying to let you know how things work
> > so you can successfully get your issue resolved.
> >
> > About managed newsgroups. There is no difference between this newsgroup and
> > a managed newsgroup. They are the same thing (whether you use a web
> > interface or a outlook express). To have your posting to be included under
> > the managed newsgroup support terms (I believe it is within 2 business days)
> > you have to do two things.
> > - you have to initiate the posting. The software they use to manage the
> > process only looks at whoever started the thread.
> > - the return email address has to be the fake one registered as part of the
> > managed newsgroup process. I'm not positive but looking at your email
> > address for your post it does not look to me like it is the fake one
> > registered with MS. If they do not see the one that has been registered with
> > them then it is ignored. Note that this is not the email address that the
> > MSDN subscription has for you (i.e. it is NOT the passport email address,
> > you have to specifically register an additional fake one that is
> > specifically for the managed newsgroup support).
> >
> > Go here:
> > http://msdn.microsoft.com/newsgroups/managed/
> >
> > Login with passport
> >
> > Then scroll down to here:
> > Getting Started
> > The managed newsgroups are easy to use. Just follow these simple
> > instructions:
> >
> > a.. Register by creating your unique no-spam alias
> > And click on the link.
> >
> > I didn't find it real intuitive about how it operates (first posting, using
> > the alias)
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
> > >I am posting this through the "Managed NewsGroup"
> > > http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> > >
> > > and am still not getting an answer. I also have an MSDN subscription.
> > > Based upon the above postings - shouldn't I get a response back?
> > >
> > > The workaround will not work for me as we have almost a 1,000 reports that
> > > get exported to Excel. Yes - we only notced this after SP1.
> > >
> > > It is obvious that this is a bug (a pretty big one at that). I don't want
> > > to get into a "p*ss*ng contest" about this but am tired of the back and
> > > forth
> > > about submitting a report case. It is simply a bug that is relatively
> > > simple
> > > to reproduce.
> > >
> > >
> > > "Bruce L-C [MVP]" wrote:
> > >
> > >> If you have universal you need to just post via a managed newsgroup (if
> > >> you
> > >> haven't done this you post with a special fake email address that you
> > >> have
> > >> registered in MSDN website and then someone from MS will answer and take
> > >> your repro case.
> > >>
> > >> I still think you have a misconception about this newsgroup, that someone
> > >> from MS is watching every thread and that there should be some sort of
> > >> official statement from them. That is not how it works. If Brian happens
> > >> to
> > >> stop by then he might do something with it. I noticed that he first said
> > >> the
> > >> best thing was to get product support involved and then he mentions
> > >> posting.
> > >> So he went both ways with his answer. Posting might get a response, with
> > >> managed newsgroup or product support you will get a response. Otherwise
> > >> it
> > >> is peer.
> > >> --
> > >> Bruce Loehle-Conger
> > >> MVP SQL Server Reporting Services
> > >>
> > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> > >> > Read the whole thread, Brian Welcker said "you can post it here but
> > >> > for
> > >> us
> > >> > to repro, we would need more than a general problem statement" etc.
> > >> > This
> > >> is
> > >> > exactly what I did way back (I found my old file and posted it again).
> > >> > The
> > >> > same issue crops up, actually frequently, and an MS employee does not
> > >> > say
> > >> > it's a bug, don't they know yet, or do they only tell people that
> > >> > contact
> > >> > the product support team?
> > >> >
> > >> > Our company has a universal MSDN subscription, and I am not hunting
> > >> > this
> > >> > issue, I bumped into the thread by accident, but could not keep quiet -
> > >> > something walks and quacks like a duck.
> > >> >
> > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> > >> > > I just changed my view to see all messages and I then see that this
> > >> > > is a
> > >> > > continuation of a posting from awhile back.
> > >> > >
> > >> > > It sounds like
> > >> > > 1. you have a work around.
> > >> > > 2. you want support from this newsgroup for your problem
> > >> > > 3. you don't want to submit a support incident
> > >> > >
> > >> > > So, however much you feel like #2 should be happening for you, that
> > >> isn't
> > >> > > how the newsgroup is setup to operate. You either need to open an
> > >> incident
> > >> > > or have an msdn subscription. The only people that get any support
> > >> > > other
> > >> > > than peer support is if you are an MSDN subscription holder in which
> > >> case
> > >> > > you this newsgroup is part of the managed newsgroups.
> > >> > >
> > >> > >
> > >> > > --
> > >> > > Bruce Loehle-Conger
> > >> > > MVP SQL Server Reporting Services
> > >> > >
> > >> > >
> > >> > >
> > >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> > >> > > > If opening a support case would have fixed the problem this month,
> > >> then
> > >> > it
> > >> > > > might have been worth the effort.
> > >> > > > I posted this problem just after the release of SP1 (without SP1
> > >> > > > one
> > >> > > cannot
> > >> > > > export to Excel 2000), many others posted it since then, and even
> > >> > > > if I
> > >> > > filed
> > >> > > > an incident then, there is no such thing as SP2 yet, and the client
> > >> > would
> > >> > > > have been off the roof by now.
> > >> > > > What I don't understand is why the MS guys don't just admit that it
> > >> > > > is
> > >> a
> > >> > > > problem and suggest a work-around or release a hot-fix or
> > >> > > > something.
> > >> As
> > >> > I
> > >> > > > said, I found sizing the stuff above the table like headers, other
> > >> text,
> > >> > > > etc, fixes the problem (haven't had any complaints from the
> > >> > > > client),
> > >> and
> > >> > > the
> > >> > > > report that looses the last row, attached to my other posting, was
> > >> fixed
> > >> > > > like this and is running at the client.
> > >> > > >
> > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > >> > > > > I suggest opening up a support case. If it is a bug you don't get
> > >> > > charged.
> > >> > > > >
> > >> > > > > --
> > >> > > > > Bruce Loehle-Conger
> > >> > > > > MVP SQL Server Reporting Services
> > >> > > > >
> > >> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> > >> > > > > message
> > >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > >> > > > > > Hopefully by now you found a work-around, but in case you did
> > >> > > > > > not,
> > >> I
> > >> > > > found
> > >> > > > > > that if I re-arrange the stuff above the table a bit, like
> > >> headers
> > >> > > and
> > >> > > > > > other text, etc, it fixes the problem.
> > >> > > > > >
> > >> > > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in
> > >> > > > > > message
> > >> > > > > > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > >> > > > > > > Hello,
> > >> > > > > > >
> > >> > > > > > > This question has been posted a few times and is DEFINITELY A
> > >> SHOW
> > >> > > > > STOPPER
> > >> > > > > > > for Reporting Services.
> > >> > > > > > >
> > >> > > > > > > When exporting to Excel - the last row can turn up missing -
> > >> > > > > > > Why
> > >> > is
> > >> > > > > > > Microsoft not responding to this?
> > >> > > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >>
> > >>
> > >>
> >
> >
> >|||I see that you started a thread with the alias on 12/1 and by now you should
have gotten a response. I have pinged someone in MS that should be able to
make sure you get a response.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"chanley54" <chanley54@.newsgroup.nospam> wrote in message
news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
> Bruce,
> Correction - I changed my alias and searched through the Managed NewsGroup
> section and it brought me to the following:
>
http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
> Again - MS says that we will have a response in two day. Sorry to beat
this
> to death.
> "chanley54" wrote:
> > Bruce,
> >
> > That's exactly what I have been doing. We do appricate the help. This
> > posting was made through the same process that you described.
> >
> > Perhaps I am doing something wrong but my return address shows the
following:
> > "chanley54@.discussions.microsoft.com"
> >
> > Regards.
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > I am trying to help you. Remember before attacking me that I help
people
> > > just for the hell of it. As such I am trying to let you know how
things work
> > > so you can successfully get your issue resolved.
> > >
> > > About managed newsgroups. There is no difference between this
newsgroup and
> > > a managed newsgroup. They are the same thing (whether you use a web
> > > interface or a outlook express). To have your posting to be included
under
> > > the managed newsgroup support terms (I believe it is within 2 business
days)
> > > you have to do two things.
> > > - you have to initiate the posting. The software they use to manage
the
> > > process only looks at whoever started the thread.
> > > - the return email address has to be the fake one registered as part
of the
> > > managed newsgroup process. I'm not positive but looking at your email
> > > address for your post it does not look to me like it is the fake one
> > > registered with MS. If they do not see the one that has been
registered with
> > > them then it is ignored. Note that this is not the email address that
the
> > > MSDN subscription has for you (i.e. it is NOT the passport email
address,
> > > you have to specifically register an additional fake one that is
> > > specifically for the managed newsgroup support).
> > >
> > > Go here:
> > > http://msdn.microsoft.com/newsgroups/managed/
> > >
> > > Login with passport
> > >
> > > Then scroll down to here:
> > > Getting Started
> > > The managed newsgroups are easy to use. Just follow these simple
> > > instructions:
> > >
> > > a.. Register by creating your unique no-spam alias
> > > And click on the link.
> > >
> > > I didn't find it real intuitive about how it operates (first posting,
using
> > > the alias)
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > > news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
> > > >I am posting this through the "Managed NewsGroup"
> > > >
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> > > >
> > > > and am still not getting an answer. I also have an MSDN
subscription.
> > > > Based upon the above postings - shouldn't I get a response back?
> > > >
> > > > The workaround will not work for me as we have almost a 1,000
reports that
> > > > get exported to Excel. Yes - we only notced this after SP1.
> > > >
> > > > It is obvious that this is a bug (a pretty big one at that). I
don't want
> > > > to get into a "p*ss*ng contest" about this but am tired of the back
and
> > > > forth
> > > > about submitting a report case. It is simply a bug that is
relatively
> > > > simple
> > > > to reproduce.
> > > >
> > > >
> > > > "Bruce L-C [MVP]" wrote:
> > > >
> > > >> If you have universal you need to just post via a managed newsgroup
(if
> > > >> you
> > > >> haven't done this you post with a special fake email address that
you
> > > >> have
> > > >> registered in MSDN website and then someone from MS will answer and
take
> > > >> your repro case.
> > > >>
> > > >> I still think you have a misconception about this newsgroup, that
someone
> > > >> from MS is watching every thread and that there should be some sort
of
> > > >> official statement from them. That is not how it works. If Brian
happens
> > > >> to
> > > >> stop by then he might do something with it. I noticed that he first
said
> > > >> the
> > > >> best thing was to get product support involved and then he mentions
> > > >> posting.
> > > >> So he went both ways with his answer. Posting might get a response,
with
> > > >> managed newsgroup or product support you will get a response.
Otherwise
> > > >> it
> > > >> is peer.
> > > >> --
> > > >> Bruce Loehle-Conger
> > > >> MVP SQL Server Reporting Services
> > > >>
> > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> > > >> > Read the whole thread, Brian Welcker said "you can post it here
but
> > > >> > for
> > > >> us
> > > >> > to repro, we would need more than a general problem statement"
etc.
> > > >> > This
> > > >> is
> > > >> > exactly what I did way back (I found my old file and posted it
again).
> > > >> > The
> > > >> > same issue crops up, actually frequently, and an MS employee does
not
> > > >> > say
> > > >> > it's a bug, don't they know yet, or do they only tell people that
> > > >> > contact
> > > >> > the product support team?
> > > >> >
> > > >> > Our company has a universal MSDN subscription, and I am not
hunting
> > > >> > this
> > > >> > issue, I bumped into the thread by accident, but could not keep
quiet -
> > > >> > something walks and quacks like a duck.
> > > >> >
> > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> > > >> > > I just changed my view to see all messages and I then see that
this
> > > >> > > is a
> > > >> > > continuation of a posting from awhile back.
> > > >> > >
> > > >> > > It sounds like
> > > >> > > 1. you have a work around.
> > > >> > > 2. you want support from this newsgroup for your problem
> > > >> > > 3. you don't want to submit a support incident
> > > >> > >
> > > >> > > So, however much you feel like #2 should be happening for you,
that
> > > >> isn't
> > > >> > > how the newsgroup is setup to operate. You either need to open
an
> > > >> incident
> > > >> > > or have an msdn subscription. The only people that get any
support
> > > >> > > other
> > > >> > > than peer support is if you are an MSDN subscription holder in
which
> > > >> case
> > > >> > > you this newsgroup is part of the managed newsgroups.
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Bruce Loehle-Conger
> > > >> > > MVP SQL Server Reporting Services
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
message
> > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> > > >> > > > If opening a support case would have fixed the problem this
month,
> > > >> then
> > > >> > it
> > > >> > > > might have been worth the effort.
> > > >> > > > I posted this problem just after the release of SP1 (without
SP1
> > > >> > > > one
> > > >> > > cannot
> > > >> > > > export to Excel 2000), many others posted it since then, and
even
> > > >> > > > if I
> > > >> > > filed
> > > >> > > > an incident then, there is no such thing as SP2 yet, and the
client
> > > >> > would
> > > >> > > > have been off the roof by now.
> > > >> > > > What I don't understand is why the MS guys don't just admit
that it
> > > >> > > > is
> > > >> a
> > > >> > > > problem and suggest a work-around or release a hot-fix or
> > > >> > > > something.
> > > >> As
> > > >> > I
> > > >> > > > said, I found sizing the stuff above the table like headers,
other
> > > >> text,
> > > >> > > > etc, fixes the problem (haven't had any complaints from the
> > > >> > > > client),
> > > >> and
> > > >> > > the
> > > >> > > > report that looses the last row, attached to my other
posting, was
> > > >> fixed
> > > >> > > > like this and is running at the client.
> > > >> > > >
> > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
message
> > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > > >> > > > > I suggest opening up a support case. If it is a bug you
don't get
> > > >> > > charged.
> > > >> > > > >
> > > >> > > > > --
> > > >> > > > > Bruce Loehle-Conger
> > > >> > > > > MVP SQL Server Reporting Services
> > > >> > > > >
> > > >> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> > > >> > > > > message
> > > >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > > >> > > > > > Hopefully by now you found a work-around, but in case you
did
> > > >> > > > > > not,
> > > >> I
> > > >> > > > found
> > > >> > > > > > that if I re-arrange the stuff above the table a bit,
like
> > > >> headers
> > > >> > > and
> > > >> > > > > > other text, etc, it fixes the problem.
> > > >> > > > > >
> > > >> > > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote
in
> > > >> > > > > > message
> > > >> > > > > >
news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > >> > > > > > > Hello,
> > > >> > > > > > >
> > > >> > > > > > > This question has been posted a few times and is
DEFINITELY A
> > > >> SHOW
> > > >> > > > > STOPPER
> > > >> > > > > > > for Reporting Services.
> > > >> > > > > > >
> > > >> > > > > > > When exporting to Excel - the last row can turn up
missing -
> > > >> > > > > > > Why
> > > >> > is
> > > >> > > > > > > Microsoft not responding to this?
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > > >
> > > >> > >
> > > >> > >
> > > >> >
> > > >> >
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||I used my MS contact and here is what he had to say:
> This customer did not register the posting alias he is using. You don't
use
> a registered alias, the MSDN team doesn't know who you are.
> Here are instructions for registering:
> 1. Use the passport associated with your MSDN subscription to login at
> http://msdn.microsoft.com/subscriptions/
> 2. On the What's Hot page, click the >here< link at the end of the first
> paragraph of the "Unlimited Support" section, which takes you to the
> registration page
> 3. Pick a nickname and domain. For example, you could use johndoe for the
> Nickname and @.nospam.nospam as the domain. Click the [Submit] button and
it
> should register johndoe@.nospam.nospam as your no-spam alias. That alias
may
> or may not be available. We are experiencing an intermittent problem with
> this page where a link goes down and rejects all submissions. If the alias
> you select gets rejected, please try waiting 10-15 minutes before trying
> again.
> When you successfully register we attempt to popup a page with more
> information. It explains how to configure your profile, among other
things.
> If you have popups blocked, the link is:
> http://msdn.microsoft.com/subscriptions/managednewsgroups/
> He should contact ngmsdnfb@.microsoft.com but I've sent mail to them asking
> them to find somebody to look at this post.
Bruce Loehle-Conger
MVP SQL Server Reporting Services|||If this thing takes off on some other group or if you manage to get a
response from the MS guys, do you mind sending me an email?
Thanks,
Chris.
"chanley54" <chanley54@.newsgroup.nospam> wrote in message
news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
> Bruce,
> Correction - I changed my alias and searched through the Managed NewsGroup
> section and it brought me to the following:
>
http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
> Again - MS says that we will have a response in two day. Sorry to beat
this
> to death.
> "chanley54" wrote:
> > Bruce,
> >
> > That's exactly what I have been doing. We do appricate the help. This
> > posting was made through the same process that you described.
> >
> > Perhaps I am doing something wrong but my return address shows the
following:
> > "chanley54@.discussions.microsoft.com"
> >
> > Regards.
> >
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > I am trying to help you. Remember before attacking me that I help
people
> > > just for the hell of it. As such I am trying to let you know how
things work
> > > so you can successfully get your issue resolved.
> > >
> > > About managed newsgroups. There is no difference between this
newsgroup and
> > > a managed newsgroup. They are the same thing (whether you use a web
> > > interface or a outlook express). To have your posting to be included
under
> > > the managed newsgroup support terms (I believe it is within 2 business
days)
> > > you have to do two things.
> > > - you have to initiate the posting. The software they use to manage
the
> > > process only looks at whoever started the thread.
> > > - the return email address has to be the fake one registered as part
of the
> > > managed newsgroup process. I'm not positive but looking at your email
> > > address for your post it does not look to me like it is the fake one
> > > registered with MS. If they do not see the one that has been
registered with
> > > them then it is ignored. Note that this is not the email address that
the
> > > MSDN subscription has for you (i.e. it is NOT the passport email
address,
> > > you have to specifically register an additional fake one that is
> > > specifically for the managed newsgroup support).
> > >
> > > Go here:
> > > http://msdn.microsoft.com/newsgroups/managed/
> > >
> > > Login with passport
> > >
> > > Then scroll down to here:
> > > Getting Started
> > > The managed newsgroups are easy to use. Just follow these simple
> > > instructions:
> > >
> > > a.. Register by creating your unique no-spam alias
> > > And click on the link.
> > >
> > > I didn't find it real intuitive about how it operates (first posting,
using
> > > the alias)
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > > news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
> > > >I am posting this through the "Managed NewsGroup"
> > > >
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> > > >
> > > > and am still not getting an answer. I also have an MSDN
subscription.
> > > > Based upon the above postings - shouldn't I get a response back?
> > > >
> > > > The workaround will not work for me as we have almost a 1,000
reports that
> > > > get exported to Excel. Yes - we only notced this after SP1.
> > > >
> > > > It is obvious that this is a bug (a pretty big one at that). I
don't want
> > > > to get into a "p*ss*ng contest" about this but am tired of the back
and
> > > > forth
> > > > about submitting a report case. It is simply a bug that is
relatively
> > > > simple
> > > > to reproduce.
> > > >
> > > >
> > > > "Bruce L-C [MVP]" wrote:
> > > >
> > > >> If you have universal you need to just post via a managed newsgroup
(if
> > > >> you
> > > >> haven't done this you post with a special fake email address that
you
> > > >> have
> > > >> registered in MSDN website and then someone from MS will answer and
take
> > > >> your repro case.
> > > >>
> > > >> I still think you have a misconception about this newsgroup, that
someone
> > > >> from MS is watching every thread and that there should be some sort
of
> > > >> official statement from them. That is not how it works. If Brian
happens
> > > >> to
> > > >> stop by then he might do something with it. I noticed that he first
said
> > > >> the
> > > >> best thing was to get product support involved and then he mentions
> > > >> posting.
> > > >> So he went both ways with his answer. Posting might get a response,
with
> > > >> managed newsgroup or product support you will get a response.
Otherwise
> > > >> it
> > > >> is peer.
> > > >> --
> > > >> Bruce Loehle-Conger
> > > >> MVP SQL Server Reporting Services
> > > >>
> > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> > > >> > Read the whole thread, Brian Welcker said "you can post it here
but
> > > >> > for
> > > >> us
> > > >> > to repro, we would need more than a general problem statement"
etc.
> > > >> > This
> > > >> is
> > > >> > exactly what I did way back (I found my old file and posted it
again).
> > > >> > The
> > > >> > same issue crops up, actually frequently, and an MS employee does
not
> > > >> > say
> > > >> > it's a bug, don't they know yet, or do they only tell people that
> > > >> > contact
> > > >> > the product support team?
> > > >> >
> > > >> > Our company has a universal MSDN subscription, and I am not
hunting
> > > >> > this
> > > >> > issue, I bumped into the thread by accident, but could not keep
quiet -
> > > >> > something walks and quacks like a duck.
> > > >> >
> > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> > > >> > > I just changed my view to see all messages and I then see that
this
> > > >> > > is a
> > > >> > > continuation of a posting from awhile back.
> > > >> > >
> > > >> > > It sounds like
> > > >> > > 1. you have a work around.
> > > >> > > 2. you want support from this newsgroup for your problem
> > > >> > > 3. you don't want to submit a support incident
> > > >> > >
> > > >> > > So, however much you feel like #2 should be happening for you,
that
> > > >> isn't
> > > >> > > how the newsgroup is setup to operate. You either need to open
an
> > > >> incident
> > > >> > > or have an msdn subscription. The only people that get any
support
> > > >> > > other
> > > >> > > than peer support is if you are an MSDN subscription holder in
which
> > > >> case
> > > >> > > you this newsgroup is part of the managed newsgroups.
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Bruce Loehle-Conger
> > > >> > > MVP SQL Server Reporting Services
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
message
> > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> > > >> > > > If opening a support case would have fixed the problem this
month,
> > > >> then
> > > >> > it
> > > >> > > > might have been worth the effort.
> > > >> > > > I posted this problem just after the release of SP1 (without
SP1
> > > >> > > > one
> > > >> > > cannot
> > > >> > > > export to Excel 2000), many others posted it since then, and
even
> > > >> > > > if I
> > > >> > > filed
> > > >> > > > an incident then, there is no such thing as SP2 yet, and the
client
> > > >> > would
> > > >> > > > have been off the roof by now.
> > > >> > > > What I don't understand is why the MS guys don't just admit
that it
> > > >> > > > is
> > > >> a
> > > >> > > > problem and suggest a work-around or release a hot-fix or
> > > >> > > > something.
> > > >> As
> > > >> > I
> > > >> > > > said, I found sizing the stuff above the table like headers,
other
> > > >> text,
> > > >> > > > etc, fixes the problem (haven't had any complaints from the
> > > >> > > > client),
> > > >> and
> > > >> > > the
> > > >> > > > report that looses the last row, attached to my other
posting, was
> > > >> fixed
> > > >> > > > like this and is running at the client.
> > > >> > > >
> > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
message
> > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > > >> > > > > I suggest opening up a support case. If it is a bug you
don't get
> > > >> > > charged.
> > > >> > > > >
> > > >> > > > > --
> > > >> > > > > Bruce Loehle-Conger
> > > >> > > > > MVP SQL Server Reporting Services
> > > >> > > > >
> > > >> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> > > >> > > > > message
> > > >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > > >> > > > > > Hopefully by now you found a work-around, but in case you
did
> > > >> > > > > > not,
> > > >> I
> > > >> > > > found
> > > >> > > > > > that if I re-arrange the stuff above the table a bit,
like
> > > >> headers
> > > >> > > and
> > > >> > > > > > other text, etc, it fixes the problem.
> > > >> > > > > >
> > > >> > > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote
in
> > > >> > > > > > message
> > > >> > > > > >
news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > >> > > > > > > Hello,
> > > >> > > > > > >
> > > >> > > > > > > This question has been posted a few times and is
DEFINITELY A
> > > >> SHOW
> > > >> > > > > STOPPER
> > > >> > > > > > > for Reporting Services.
> > > >> > > > > > >
> > > >> > > > > > > When exporting to Excel - the last row can turn up
missing -
> > > >> > > > > > > Why
> > > >> > is
> > > >> > > > > > > Microsoft not responding to this?
> > > >> > > > > > >
> > > >> > > > > >
> > > >> > > > > >
> > > >> > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > > >
> > > >> > >
> > > >> > >
> > > >> >
> > > >> >
> > > >>
> > > >>
> > > >>
> > >
> > >
> > >|||Absolutely - I've got users breathing down my neck on this one.
-- Chris
"Chris Botha" wrote:
> If this thing takes off on some other group or if you manage to get a
> response from the MS guys, do you mind sending me an email?
> Thanks,
> Chris.
> "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
> > Bruce,
> >
> > Correction - I changed my alias and searched through the Managed NewsGroup
> > section and it brought me to the following:
> >
> >
> http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
> >
> > Again - MS says that we will have a response in two day. Sorry to beat
> this
> > to death.
> >
> > "chanley54" wrote:
> >
> > > Bruce,
> > >
> > > That's exactly what I have been doing. We do appricate the help. This
> > > posting was made through the same process that you described.
> > >
> > > Perhaps I am doing something wrong but my return address shows the
> following:
> > > "chanley54@.discussions.microsoft.com"
> > >
> > > Regards.
> > >
> > >
> > > "Bruce L-C [MVP]" wrote:
> > >
> > > > I am trying to help you. Remember before attacking me that I help
> people
> > > > just for the hell of it. As such I am trying to let you know how
> things work
> > > > so you can successfully get your issue resolved.
> > > >
> > > > About managed newsgroups. There is no difference between this
> newsgroup and
> > > > a managed newsgroup. They are the same thing (whether you use a web
> > > > interface or a outlook express). To have your posting to be included
> under
> > > > the managed newsgroup support terms (I believe it is within 2 business
> days)
> > > > you have to do two things.
> > > > - you have to initiate the posting. The software they use to manage
> the
> > > > process only looks at whoever started the thread.
> > > > - the return email address has to be the fake one registered as part
> of the
> > > > managed newsgroup process. I'm not positive but looking at your email
> > > > address for your post it does not look to me like it is the fake one
> > > > registered with MS. If they do not see the one that has been
> registered with
> > > > them then it is ignored. Note that this is not the email address that
> the
> > > > MSDN subscription has for you (i.e. it is NOT the passport email
> address,
> > > > you have to specifically register an additional fake one that is
> > > > specifically for the managed newsgroup support).
> > > >
> > > > Go here:
> > > > http://msdn.microsoft.com/newsgroups/managed/
> > > >
> > > > Login with passport
> > > >
> > > > Then scroll down to here:
> > > > Getting Started
> > > > The managed newsgroups are easy to use. Just follow these simple
> > > > instructions:
> > > >
> > > > a.. Register by creating your unique no-spam alias
> > > > And click on the link.
> > > >
> > > > I didn't find it real intuitive about how it operates (first posting,
> using
> > > > the alias)
> > > >
> > > >
> > > > --
> > > > Bruce Loehle-Conger
> > > > MVP SQL Server Reporting Services
> > > >
> > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > > > news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
> > > > >I am posting this through the "Managed NewsGroup"
> > > > >
> http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> > > > >
> > > > > and am still not getting an answer. I also have an MSDN
> subscription.
> > > > > Based upon the above postings - shouldn't I get a response back?
> > > > >
> > > > > The workaround will not work for me as we have almost a 1,000
> reports that
> > > > > get exported to Excel. Yes - we only notced this after SP1.
> > > > >
> > > > > It is obvious that this is a bug (a pretty big one at that). I
> don't want
> > > > > to get into a "p*ss*ng contest" about this but am tired of the back
> and
> > > > > forth
> > > > > about submitting a report case. It is simply a bug that is
> relatively
> > > > > simple
> > > > > to reproduce.
> > > > >
> > > > >
> > > > > "Bruce L-C [MVP]" wrote:
> > > > >
> > > > >> If you have universal you need to just post via a managed newsgroup
> (if
> > > > >> you
> > > > >> haven't done this you post with a special fake email address that
> you
> > > > >> have
> > > > >> registered in MSDN website and then someone from MS will answer and
> take
> > > > >> your repro case.
> > > > >>
> > > > >> I still think you have a misconception about this newsgroup, that
> someone
> > > > >> from MS is watching every thread and that there should be some sort
> of
> > > > >> official statement from them. That is not how it works. If Brian
> happens
> > > > >> to
> > > > >> stop by then he might do something with it. I noticed that he first
> said
> > > > >> the
> > > > >> best thing was to get product support involved and then he mentions
> > > > >> posting.
> > > > >> So he went both ways with his answer. Posting might get a response,
> with
> > > > >> managed newsgroup or product support you will get a response.
> Otherwise
> > > > >> it
> > > > >> is peer.
> > > > >> --
> > > > >> Bruce Loehle-Conger
> > > > >> MVP SQL Server Reporting Services
> > > > >>
> > > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> > > > >> > Read the whole thread, Brian Welcker said "you can post it here
> but
> > > > >> > for
> > > > >> us
> > > > >> > to repro, we would need more than a general problem statement"
> etc.
> > > > >> > This
> > > > >> is
> > > > >> > exactly what I did way back (I found my old file and posted it
> again).
> > > > >> > The
> > > > >> > same issue crops up, actually frequently, and an MS employee does
> not
> > > > >> > say
> > > > >> > it's a bug, don't they know yet, or do they only tell people that
> > > > >> > contact
> > > > >> > the product support team?
> > > > >> >
> > > > >> > Our company has a universal MSDN subscription, and I am not
> hunting
> > > > >> > this
> > > > >> > issue, I bumped into the thread by accident, but could not keep
> quiet -
> > > > >> > something walks and quacks like a duck.
> > > > >> >
> > > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> > > > >> > > I just changed my view to see all messages and I then see that
> this
> > > > >> > > is a
> > > > >> > > continuation of a posting from awhile back.
> > > > >> > >
> > > > >> > > It sounds like
> > > > >> > > 1. you have a work around.
> > > > >> > > 2. you want support from this newsgroup for your problem
> > > > >> > > 3. you don't want to submit a support incident
> > > > >> > >
> > > > >> > > So, however much you feel like #2 should be happening for you,
> that
> > > > >> isn't
> > > > >> > > how the newsgroup is setup to operate. You either need to open
> an
> > > > >> incident
> > > > >> > > or have an msdn subscription. The only people that get any
> support
> > > > >> > > other
> > > > >> > > than peer support is if you are an MSDN subscription holder in
> which
> > > > >> case
> > > > >> > > you this newsgroup is part of the managed newsgroups.
> > > > >> > >
> > > > >> > >
> > > > >> > > --
> > > > >> > > Bruce Loehle-Conger
> > > > >> > > MVP SQL Server Reporting Services
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> message
> > > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> > > > >> > > > If opening a support case would have fixed the problem this
> month,
> > > > >> then
> > > > >> > it
> > > > >> > > > might have been worth the effort.
> > > > >> > > > I posted this problem just after the release of SP1 (without
> SP1
> > > > >> > > > one
> > > > >> > > cannot
> > > > >> > > > export to Excel 2000), many others posted it since then, and
> even
> > > > >> > > > if I
> > > > >> > > filed
> > > > >> > > > an incident then, there is no such thing as SP2 yet, and the
> client
> > > > >> > would
> > > > >> > > > have been off the roof by now.
> > > > >> > > > What I don't understand is why the MS guys don't just admit
> that it
> > > > >> > > > is
> > > > >> a
> > > > >> > > > problem and suggest a work-around or release a hot-fix or
> > > > >> > > > something.
> > > > >> As
> > > > >> > I
> > > > >> > > > said, I found sizing the stuff above the table like headers,
> other
> > > > >> text,
> > > > >> > > > etc, fixes the problem (haven't had any complaints from the
> > > > >> > > > client),
> > > > >> and
> > > > >> > > the
> > > > >> > > > report that looses the last row, attached to my other
> posting, was
> > > > >> fixed
> > > > >> > > > like this and is running at the client.
> > > > >> > > >
> > > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
> message
> > > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > > > >> > > > > I suggest opening up a support case. If it is a bug you
> don't get
> > > > >> > > charged.
> > > > >> > > > >
> > > > >> > > > > --
> > > > >> > > > > Bruce Loehle-Conger
> > > > >> > > > > MVP SQL Server Reporting Services
> > > > >> > > > >
> > > > >> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> > > > >> > > > > message
> > > > >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > > > >> > > > > > Hopefully by now you found a work-around, but in case you
> did
> > > > >> > > > > > not,
> > > > >> I
> > > > >> > > > found
> > > > >> > > > > > that if I re-arrange the stuff above the table a bit,
> like
> > > > >> headers
> > > > >> > > and
> > > > >> > > > > > other text, etc, it fixes the problem.
> > > > >> > > > > >
> > > > >> > > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote
> in
> > > > >> > > > > > message
> > > > >> > > > > >
> news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > > >> > > > > > > Hello,
> > > > >> > > > > > >
> > > > >> > > > > > > This question has been posted a few times and is
> DEFINITELY A
> > > > >> SHOW
> > > > >> > > > > STOPPER
> > > > >> > > > > > > for Reporting Services.
> > > > >> > > > > > >
> > > > >> > > > > > > When exporting to Excel - the last row can turn up
> missing -
> > > > >> > > > > > > Why
> > > > >> > is
> > > > >> > > > > > > Microsoft not responding to this?
> > > > >> > > > > > >
> > > > >> > > > > >
> > > > >> > > > > >
> > > > >> > > > >
> > > > >> > > > >
> > > > >> > > >
> > > > >> > > >
> > > > >> > >
> > > > >> > >
> > > > >> >
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > >
> > > >
> > > >
>
>|||Last post was 12/7/2004... Any news from MS on this one - I just bumped
into the same wall with Excel 2003 and SP1...
Cheers!
"chanley54" <chanley54@.newsgroup.nospam> wrote in message
news:26BF4F85-ED31-4DE7-9468-441B07976F2E@.microsoft.com...
> Absolutely - I've got users breathing down my neck on this one.
> -- Chris
> "Chris Botha" wrote:
> > If this thing takes off on some other group or if you manage to get a
> > response from the MS guys, do you mind sending me an email?
> > Thanks,
> >
> > Chris.
> >
> > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> > news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
> > > Bruce,
> > >
> > > Correction - I changed my alias and searched through the Managed
NewsGroup
> > > section and it brought me to the following:
> > >
> > >
> >
http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
> > >
> > > Again - MS says that we will have a response in two day. Sorry to
beat
> > this
> > > to death.
> > >
> > > "chanley54" wrote:
> > >
> > > > Bruce,
> > > >
> > > > That's exactly what I have been doing. We do appricate the help.
This
> > > > posting was made through the same process that you described.
> > > >
> > > > Perhaps I am doing something wrong but my return address shows the
> > following:
> > > > "chanley54@.discussions.microsoft.com"
> > > >
> > > > Regards.
> > > >
> > > >
> > > > "Bruce L-C [MVP]" wrote:
> > > >
> > > > > I am trying to help you. Remember before attacking me that I help
> > people
> > > > > just for the hell of it. As such I am trying to let you know how
> > things work
> > > > > so you can successfully get your issue resolved.
> > > > >
> > > > > About managed newsgroups. There is no difference between this
> > newsgroup and
> > > > > a managed newsgroup. They are the same thing (whether you use a
web
> > > > > interface or a outlook express). To have your posting to be
included
> > under
> > > > > the managed newsgroup support terms (I believe it is within 2
business
> > days)
> > > > > you have to do two things.
> > > > > - you have to initiate the posting. The software they use to
manage
> > the
> > > > > process only looks at whoever started the thread.
> > > > > - the return email address has to be the fake one registered as
part
> > of the
> > > > > managed newsgroup process. I'm not positive but looking at your
email
> > > > > address for your post it does not look to me like it is the fake
one
> > > > > registered with MS. If they do not see the one that has been
> > registered with
> > > > > them then it is ignored. Note that this is not the email address
that
> > the
> > > > > MSDN subscription has for you (i.e. it is NOT the passport email
> > address,
> > > > > you have to specifically register an additional fake one that is
> > > > > specifically for the managed newsgroup support).
> > > > >
> > > > > Go here:
> > > > > http://msdn.microsoft.com/newsgroups/managed/
> > > > >
> > > > > Login with passport
> > > > >
> > > > > Then scroll down to here:
> > > > > Getting Started
> > > > > The managed newsgroups are easy to use. Just follow these simple
> > > > > instructions:
> > > > >
> > > > > a.. Register by creating your unique no-spam alias
> > > > > And click on the link.
> > > > >
> > > > > I didn't find it real intuitive about how it operates (first
posting,
> > using
> > > > > the alias)
> > > > >
> > > > >
> > > > > --
> > > > > Bruce Loehle-Conger
> > > > > MVP SQL Server Reporting Services
> > > > >
> > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > > > > news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
> > > > > >I am posting this through the "Managed NewsGroup"
> > > > > >
> >
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> > > > > >
> > > > > > and am still not getting an answer. I also have an MSDN
> > subscription.
> > > > > > Based upon the above postings - shouldn't I get a response back?
> > > > > >
> > > > > > The workaround will not work for me as we have almost a 1,000
> > reports that
> > > > > > get exported to Excel. Yes - we only notced this after SP1.
> > > > > >
> > > > > > It is obvious that this is a bug (a pretty big one at that). I
> > don't want
> > > > > > to get into a "p*ss*ng contest" about this but am tired of the
back
> > and
> > > > > > forth
> > > > > > about submitting a report case. It is simply a bug that is
> > relatively
> > > > > > simple
> > > > > > to reproduce.
> > > > > >
> > > > > >
> > > > > > "Bruce L-C [MVP]" wrote:
> > > > > >
> > > > > >> If you have universal you need to just post via a managed
newsgroup
> > (if
> > > > > >> you
> > > > > >> haven't done this you post with a special fake email address
that
> > you
> > > > > >> have
> > > > > >> registered in MSDN website and then someone from MS will answer
and
> > take
> > > > > >> your repro case.
> > > > > >>
> > > > > >> I still think you have a misconception about this newsgroup,
that
> > someone
> > > > > >> from MS is watching every thread and that there should be some
sort
> > of
> > > > > >> official statement from them. That is not how it works. If
Brian
> > happens
> > > > > >> to
> > > > > >> stop by then he might do something with it. I noticed that he
first
> > said
> > > > > >> the
> > > > > >> best thing was to get product support involved and then he
mentions
> > > > > >> posting.
> > > > > >> So he went both ways with his answer. Posting might get a
response,
> > with
> > > > > >> managed newsgroup or product support you will get a response.
> > Otherwise
> > > > > >> it
> > > > > >> is peer.
> > > > > >> --
> > > > > >> Bruce Loehle-Conger
> > > > > >> MVP SQL Server Reporting Services
> > > > > >>
> > > > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
message
> > > > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> > > > > >> > Read the whole thread, Brian Welcker said "you can post it
here
> > but
> > > > > >> > for
> > > > > >> us
> > > > > >> > to repro, we would need more than a general problem
statement"
> > etc.
> > > > > >> > This
> > > > > >> is
> > > > > >> > exactly what I did way back (I found my old file and posted
it
> > again).
> > > > > >> > The
> > > > > >> > same issue crops up, actually frequently, and an MS employee
does
> > not
> > > > > >> > say
> > > > > >> > it's a bug, don't they know yet, or do they only tell people
that
> > > > > >> > contact
> > > > > >> > the product support team?
> > > > > >> >
> > > > > >> > Our company has a universal MSDN subscription, and I am not
> > hunting
> > > > > >> > this
> > > > > >> > issue, I bumped into the thread by accident, but could not
keep
> > quiet -
> > > > > >> > something walks and quacks like a duck.
> > > > > >> >
> > > > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
message
> > > > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> > > > > >> > > I just changed my view to see all messages and I then see
that
> > this
> > > > > >> > > is a
> > > > > >> > > continuation of a posting from awhile back.
> > > > > >> > >
> > > > > >> > > It sounds like
> > > > > >> > > 1. you have a work around.
> > > > > >> > > 2. you want support from this newsgroup for your problem
> > > > > >> > > 3. you don't want to submit a support incident
> > > > > >> > >
> > > > > >> > > So, however much you feel like #2 should be happening for
you,
> > that
> > > > > >> isn't
> > > > > >> > > how the newsgroup is setup to operate. You either need to
open
> > an
> > > > > >> incident
> > > > > >> > > or have an msdn subscription. The only people that get any
> > support
> > > > > >> > > other
> > > > > >> > > than peer support is if you are an MSDN subscription holder
in
> > which
> > > > > >> case
> > > > > >> > > you this newsgroup is part of the managed newsgroups.
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > --
> > > > > >> > > Bruce Loehle-Conger
> > > > > >> > > MVP SQL Server Reporting Services
> > > > > >> > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> > message
> > > > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> > > > > >> > > > If opening a support case would have fixed the problem
this
> > month,
> > > > > >> then
> > > > > >> > it
> > > > > >> > > > might have been worth the effort.
> > > > > >> > > > I posted this problem just after the release of SP1
(without
> > SP1
> > > > > >> > > > one
> > > > > >> > > cannot
> > > > > >> > > > export to Excel 2000), many others posted it since then,
and
> > even
> > > > > >> > > > if I
> > > > > >> > > filed
> > > > > >> > > > an incident then, there is no such thing as SP2 yet, and
the
> > client
> > > > > >> > would
> > > > > >> > > > have been off the roof by now.
> > > > > >> > > > What I don't understand is why the MS guys don't just
admit
> > that it
> > > > > >> > > > is
> > > > > >> a
> > > > > >> > > > problem and suggest a work-around or release a hot-fix or
> > > > > >> > > > something.
> > > > > >> As
> > > > > >> > I
> > > > > >> > > > said, I found sizing the stuff above the table like
headers,
> > other
> > > > > >> text,
> > > > > >> > > > etc, fixes the problem (haven't had any complaints from
the
> > > > > >> > > > client),
> > > > > >> and
> > > > > >> > > the
> > > > > >> > > > report that looses the last row, attached to my other
> > posting, was
> > > > > >> fixed
> > > > > >> > > > like this and is running at the client.
> > > > > >> > > >
> > > > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
> > message
> > > > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > > > > >> > > > > I suggest opening up a support case. If it is a bug you
> > don't get
> > > > > >> > > charged.
> > > > > >> > > > >
> > > > > >> > > > > --
> > > > > >> > > > > Bruce Loehle-Conger
> > > > > >> > > > > MVP SQL Server Reporting Services
> > > > > >> > > > >
> > > > > >> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
wrote in
> > > > > >> > > > > message
> > > > > >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > > > > >> > > > > > Hopefully by now you found a work-around, but in case
you
> > did
> > > > > >> > > > > > not,
> > > > > >> I
> > > > > >> > > > found
> > > > > >> > > > > > that if I re-arrange the stuff above the table a
bit,
> > like
> > > > > >> headers
> > > > > >> > > and
> > > > > >> > > > > > other text, etc, it fixes the problem.
> > > > > >> > > > > >
> > > > > >> > > > > > "chanley54" <chanley54@.discussions.microsoft.com>
wrote
> > in
> > > > > >> > > > > > message
> > > > > >> > > > > >
> > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > > > >> > > > > > > Hello,
> > > > > >> > > > > > >
> > > > > >> > > > > > > This question has been posted a few times and is
> > DEFINITELY A
> > > > > >> SHOW
> > > > > >> > > > > STOPPER
> > > > > >> > > > > > > for Reporting Services.
> > > > > >> > > > > > >
> > > > > >> > > > > > > When exporting to Excel - the last row can turn up
> > missing -
> > > > > >> > > > > > > Why
> > > > > >> > is
> > > > > >> > > > > > > Microsoft not responding to this?
> > > > > >> > > > > > >
> > > > > >> > > > > >
> > > > > >> > > > > >
> > > > > >> > > > >
> > > > > >> > > > >
> > > > > >> > > >
> > > > > >> > > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> >
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >>
> > > > >
> > > > >
> > > > >
> >
> >
> >|||Ever heard the story "The Emperor's new clothes", where the tailor said
that anybody that could not see the emperor's new clothes did not have good
taste, or something like that, while the emperor was actually naked? This
issue reminds me of it. When I bumped into it for the 1st time just after
SP1, one then eager MS guy said he would look into it, but must have been
side tracked, or was told that there is no such bug, and since then, every
so often, some desperate soul will post this issue, and then the MS guys
won't touch it. It is like say nothing, then there is nothing. I was
thinking that maybe it was the Chief of Reporting Services or someone who
knows someone important, close to Bill maybe, programmed this part, and that
they are not allowed to tell.
Just look down the newsgroup to a post on 1/29/2005 8:55 AM (5 days ago) by
"chanley54", titled "For MS Development Team - SP2", where he asked if the
issue is fixed in SP2, silence from the MS camp.
The following link points to a list of bugs that are fixed by SP2 Beta,
dated 16 Dec 2004, and this issue is not mentioned there, however they
mention that "the list may be updated".
http://support.microsoft.com/default.aspx?scid=kb;en-us;889640
"SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
news:OlA62DmCFHA.1432@.tk2msftngp13.phx.gbl...
> Last post was 12/7/2004... Any news from MS on this one - I just bumped
> into the same wall with Excel 2003 and SP1...
> Cheers!
> "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> news:26BF4F85-ED31-4DE7-9468-441B07976F2E@.microsoft.com...
>> Absolutely - I've got users breathing down my neck on this one.
>> -- Chris
>> "Chris Botha" wrote:
>> > If this thing takes off on some other group or if you manage to get a
>> > response from the MS guys, do you mind sending me an email?
>> > Thanks,
>> >
>> > Chris.
>> >
>> > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
>> > news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
>> > > Bruce,
>> > >
>> > > Correction - I changed my alias and searched through the Managed
> NewsGroup
>> > > section and it brought me to the following:
>> > >
>> > >
>> >
> http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
>> > >
>> > > Again - MS says that we will have a response in two day. Sorry to
> beat
>> > this
>> > > to death.
>> > >
>> > > "chanley54" wrote:
>> > >
>> > > > Bruce,
>> > > >
>> > > > That's exactly what I have been doing. We do appricate the help.
> This
>> > > > posting was made through the same process that you described.
>> > > >
>> > > > Perhaps I am doing something wrong but my return address shows the
>> > following:
>> > > > "chanley54@.discussions.microsoft.com"
>> > > >
>> > > > Regards.
>> > > >
>> > > >
>> > > > "Bruce L-C [MVP]" wrote:
>> > > >
>> > > > > I am trying to help you. Remember before attacking me that I help
>> > people
>> > > > > just for the hell of it. As such I am trying to let you know how
>> > things work
>> > > > > so you can successfully get your issue resolved.
>> > > > >
>> > > > > About managed newsgroups. There is no difference between this
>> > newsgroup and
>> > > > > a managed newsgroup. They are the same thing (whether you use a
> web
>> > > > > interface or a outlook express). To have your posting to be
> included
>> > under
>> > > > > the managed newsgroup support terms (I believe it is within 2
> business
>> > days)
>> > > > > you have to do two things.
>> > > > > - you have to initiate the posting. The software they use to
> manage
>> > the
>> > > > > process only looks at whoever started the thread.
>> > > > > - the return email address has to be the fake one registered as
> part
>> > of the
>> > > > > managed newsgroup process. I'm not positive but looking at your
> email
>> > > > > address for your post it does not look to me like it is the fake
> one
>> > > > > registered with MS. If they do not see the one that has been
>> > registered with
>> > > > > them then it is ignored. Note that this is not the email address
> that
>> > the
>> > > > > MSDN subscription has for you (i.e. it is NOT the passport email
>> > address,
>> > > > > you have to specifically register an additional fake one that is
>> > > > > specifically for the managed newsgroup support).
>> > > > >
>> > > > > Go here:
>> > > > > http://msdn.microsoft.com/newsgroups/managed/
>> > > > >
>> > > > > Login with passport
>> > > > >
>> > > > > Then scroll down to here:
>> > > > > Getting Started
>> > > > > The managed newsgroups are easy to use. Just follow these simple
>> > > > > instructions:
>> > > > >
>> > > > > a.. Register by creating your unique no-spam alias
>> > > > > And click on the link.
>> > > > >
>> > > > > I didn't find it real intuitive about how it operates (first
> posting,
>> > using
>> > > > > the alias)
>> > > > >
>> > > > >
>> > > > > --
>> > > > > Bruce Loehle-Conger
>> > > > > MVP SQL Server Reporting Services
>> > > > >
>> > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in
>> > > > > message
>> > > > > news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
>> > > > > >I am posting this through the "Managed NewsGroup"
>> > > > > >
>> >
> http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
>> > > > > >
>> > > > > > and am still not getting an answer. I also have an MSDN
>> > subscription.
>> > > > > > Based upon the above postings - shouldn't I get a response
>> > > > > > back?
>> > > > > >
>> > > > > > The workaround will not work for me as we have almost a 1,000
>> > reports that
>> > > > > > get exported to Excel. Yes - we only notced this after SP1.
>> > > > > >
>> > > > > > It is obvious that this is a bug (a pretty big one at that). I
>> > don't want
>> > > > > > to get into a "p*ss*ng contest" about this but am tired of the
> back
>> > and
>> > > > > > forth
>> > > > > > about submitting a report case. It is simply a bug that is
>> > relatively
>> > > > > > simple
>> > > > > > to reproduce.
>> > > > > >
>> > > > > >
>> > > > > > "Bruce L-C [MVP]" wrote:
>> > > > > >
>> > > > > >> If you have universal you need to just post via a managed
> newsgroup
>> > (if
>> > > > > >> you
>> > > > > >> haven't done this you post with a special fake email address
> that
>> > you
>> > > > > >> have
>> > > > > >> registered in MSDN website and then someone from MS will
>> > > > > >> answer
> and
>> > take
>> > > > > >> your repro case.
>> > > > > >>
>> > > > > >> I still think you have a misconception about this newsgroup,
> that
>> > someone
>> > > > > >> from MS is watching every thread and that there should be some
> sort
>> > of
>> > > > > >> official statement from them. That is not how it works. If
> Brian
>> > happens
>> > > > > >> to
>> > > > > >> stop by then he might do something with it. I noticed that he
> first
>> > said
>> > > > > >> the
>> > > > > >> best thing was to get product support involved and then he
> mentions
>> > > > > >> posting.
>> > > > > >> So he went both ways with his answer. Posting might get a
> response,
>> > with
>> > > > > >> managed newsgroup or product support you will get a response.
>> > Otherwise
>> > > > > >> it
>> > > > > >> is peer.
>> > > > > >> --
>> > > > > >> Bruce Loehle-Conger
>> > > > > >> MVP SQL Server Reporting Services
>> > > > > >>
>> > > > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> message
>> > > > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
>> > > > > >> > Read the whole thread, Brian Welcker said "you can post it
> here
>> > but
>> > > > > >> > for
>> > > > > >> us
>> > > > > >> > to repro, we would need more than a general problem
> statement"
>> > etc.
>> > > > > >> > This
>> > > > > >> is
>> > > > > >> > exactly what I did way back (I found my old file and posted
> it
>> > again).
>> > > > > >> > The
>> > > > > >> > same issue crops up, actually frequently, and an MS employee
> does
>> > not
>> > > > > >> > say
>> > > > > >> > it's a bug, don't they know yet, or do they only tell people
> that
>> > > > > >> > contact
>> > > > > >> > the product support team?
>> > > > > >> >
>> > > > > >> > Our company has a universal MSDN subscription, and I am not
>> > hunting
>> > > > > >> > this
>> > > > > >> > issue, I bumped into the thread by accident, but could not
> keep
>> > quiet -
>> > > > > >> > something walks and quacks like a duck.
>> > > > > >> >
>> > > > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
> message
>> > > > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
>> > > > > >> > > I just changed my view to see all messages and I then see
> that
>> > this
>> > > > > >> > > is a
>> > > > > >> > > continuation of a posting from awhile back.
>> > > > > >> > >
>> > > > > >> > > It sounds like
>> > > > > >> > > 1. you have a work around.
>> > > > > >> > > 2. you want support from this newsgroup for your problem
>> > > > > >> > > 3. you don't want to submit a support incident
>> > > > > >> > >
>> > > > > >> > > So, however much you feel like #2 should be happening for
> you,
>> > that
>> > > > > >> isn't
>> > > > > >> > > how the newsgroup is setup to operate. You either need to
> open
>> > an
>> > > > > >> incident
>> > > > > >> > > or have an msdn subscription. The only people that get any
>> > support
>> > > > > >> > > other
>> > > > > >> > > than peer support is if you are an MSDN subscription
>> > > > > >> > > holder
> in
>> > which
>> > > > > >> case
>> > > > > >> > > you this newsgroup is part of the managed newsgroups.
>> > > > > >> > >
>> > > > > >> > >
>> > > > > >> > > --
>> > > > > >> > > Bruce Loehle-Conger
>> > > > > >> > > MVP SQL Server Reporting Services
>> > > > > >> > >
>> > > > > >> > >
>> > > > > >> > >
>> > > > > >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote
>> > > > > >> > > in
>> > message
>> > > > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
>> > > > > >> > > > If opening a support case would have fixed the problem
> this
>> > month,
>> > > > > >> then
>> > > > > >> > it
>> > > > > >> > > > might have been worth the effort.
>> > > > > >> > > > I posted this problem just after the release of SP1
> (without
>> > SP1
>> > > > > >> > > > one
>> > > > > >> > > cannot
>> > > > > >> > > > export to Excel 2000), many others posted it since then,
> and
>> > even
>> > > > > >> > > > if I
>> > > > > >> > > filed
>> > > > > >> > > > an incident then, there is no such thing as SP2 yet, and
> the
>> > client
>> > > > > >> > would
>> > > > > >> > > > have been off the roof by now.
>> > > > > >> > > > What I don't understand is why the MS guys don't just
> admit
>> > that it
>> > > > > >> > > > is
>> > > > > >> a
>> > > > > >> > > > problem and suggest a work-around or release a hot-fix
>> > > > > >> > > > or
>> > > > > >> > > > something.
>> > > > > >> As
>> > > > > >> > I
>> > > > > >> > > > said, I found sizing the stuff above the table like
> headers,
>> > other
>> > > > > >> text,
>> > > > > >> > > > etc, fixes the problem (haven't had any complaints from
> the
>> > > > > >> > > > client),
>> > > > > >> and
>> > > > > >> > > the
>> > > > > >> > > > report that looses the last row, attached to my other
>> > posting, was
>> > > > > >> fixed
>> > > > > >> > > > like this and is running at the client.
>> > > > > >> > > >
>> > > > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
>> > message
>> > > > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
>> > > > > >> > > > > I suggest opening up a support case. If it is a bug
>> > > > > >> > > > > you
>> > don't get
>> > > > > >> > > charged.
>> > > > > >> > > > >
>> > > > > >> > > > > --
>> > > > > >> > > > > Bruce Loehle-Conger
>> > > > > >> > > > > MVP SQL Server Reporting Services
>> > > > > >> > > > >
>> > > > > >> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> wrote in
>> > > > > >> > > > > message
>> > > > > >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
>> > > > > >> > > > > > Hopefully by now you found a work-around, but in
>> > > > > >> > > > > > case
> you
>> > did
>> > > > > >> > > > > > not,
>> > > > > >> I
>> > > > > >> > > > found
>> > > > > >> > > > > > that if I re-arrange the stuff above the table a
> bit,
>> > like
>> > > > > >> headers
>> > > > > >> > > and
>> > > > > >> > > > > > other text, etc, it fixes the problem.
>> > > > > >> > > > > >
>> > > > > >> > > > > > "chanley54" <chanley54@.discussions.microsoft.com>
> wrote
>> > in
>> > > > > >> > > > > > message
>> > > > > >> > > > > >
>> > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
>> > > > > >> > > > > > > Hello,
>> > > > > >> > > > > > >
>> > > > > >> > > > > > > This question has been posted a few times and is
>> > DEFINITELY A
>> > > > > >> SHOW
>> > > > > >> > > > > STOPPER
>> > > > > >> > > > > > > for Reporting Services.
>> > > > > >> > > > > > >
>> > > > > >> > > > > > > When exporting to Excel - the last row can turn up
>> > missing -
>> > > > > >> > > > > > > Why
>> > > > > >> > is
>> > > > > >> > > > > > > Microsoft not responding to this?
>> > > > > >> > > > > > >
>> > > > > >> > > > > >
>> > > > > >> > > > > >
>> > > > > >> > > > >
>> > > > > >> > > > >
>> > > > > >> > > >
>> > > > > >> > > >
>> > > > > >> > >
>> > > > > >> > >
>> > > > > >> >
>> > > > > >> >
>> > > > > >>
>> > > > > >>
>> > > > > >>
>> > > > >
>> > > > >
>> > > > >
>> >
>> >
>> >
>|||Brilliant! We obediently follow the procedures to get our posts noticed by
MS and... silence...
Perhaps I should open a bug using our MSDN subscription instead...
Thanks for the update and the ref to the bug list.
"Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
news:ONAxfOnCFHA.392@.TK2MSFTNGP14.phx.gbl...
> Ever heard the story "The Emperor's new clothes", where the tailor said
> that anybody that could not see the emperor's new clothes did not have
good
> taste, or something like that, while the emperor was actually naked? This
> issue reminds me of it. When I bumped into it for the 1st time just after
> SP1, one then eager MS guy said he would look into it, but must have been
> side tracked, or was told that there is no such bug, and since then, every
> so often, some desperate soul will post this issue, and then the MS guys
> won't touch it. It is like say nothing, then there is nothing. I was
> thinking that maybe it was the Chief of Reporting Services or someone who
> knows someone important, close to Bill maybe, programmed this part, and
that
> they are not allowed to tell.
> Just look down the newsgroup to a post on 1/29/2005 8:55 AM (5 days ago)
by
> "chanley54", titled "For MS Development Team - SP2", where he asked if the
> issue is fixed in SP2, silence from the MS camp.
> The following link points to a list of bugs that are fixed by SP2 Beta,
> dated 16 Dec 2004, and this issue is not mentioned there, however they
> mention that "the list may be updated".
> http://support.microsoft.com/default.aspx?scid=kb;en-us;889640
>
> "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
> news:OlA62DmCFHA.1432@.tk2msftngp13.phx.gbl...
> > Last post was 12/7/2004... Any news from MS on this one - I just bumped
> > into the same wall with Excel 2003 and SP1...
> >
> > Cheers!
> >
> > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> > news:26BF4F85-ED31-4DE7-9468-441B07976F2E@.microsoft.com...
> >> Absolutely - I've got users breathing down my neck on this one.
> >>
> >> -- Chris
> >>
> >> "Chris Botha" wrote:
> >>
> >> > If this thing takes off on some other group or if you manage to get a
> >> > response from the MS guys, do you mind sending me an email?
> >> > Thanks,
> >> >
> >> > Chris.
> >> >
> >> > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> >> > news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
> >> > > Bruce,
> >> > >
> >> > > Correction - I changed my alias and searched through the Managed
> > NewsGroup
> >> > > section and it brought me to the following:
> >> > >
> >> > >
> >> >
> >
http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
> >> > >
> >> > > Again - MS says that we will have a response in two day. Sorry to
> > beat
> >> > this
> >> > > to death.
> >> > >
> >> > > "chanley54" wrote:
> >> > >
> >> > > > Bruce,
> >> > > >
> >> > > > That's exactly what I have been doing. We do appricate the help.
> > This
> >> > > > posting was made through the same process that you described.
> >> > > >
> >> > > > Perhaps I am doing something wrong but my return address shows
the
> >> > following:
> >> > > > "chanley54@.discussions.microsoft.com"
> >> > > >
> >> > > > Regards.
> >> > > >
> >> > > >
> >> > > > "Bruce L-C [MVP]" wrote:
> >> > > >
> >> > > > > I am trying to help you. Remember before attacking me that I
help
> >> > people
> >> > > > > just for the hell of it. As such I am trying to let you know
how
> >> > things work
> >> > > > > so you can successfully get your issue resolved.
> >> > > > >
> >> > > > > About managed newsgroups. There is no difference between this
> >> > newsgroup and
> >> > > > > a managed newsgroup. They are the same thing (whether you use a
> > web
> >> > > > > interface or a outlook express). To have your posting to be
> > included
> >> > under
> >> > > > > the managed newsgroup support terms (I believe it is within 2
> > business
> >> > days)
> >> > > > > you have to do two things.
> >> > > > > - you have to initiate the posting. The software they use to
> > manage
> >> > the
> >> > > > > process only looks at whoever started the thread.
> >> > > > > - the return email address has to be the fake one registered as
> > part
> >> > of the
> >> > > > > managed newsgroup process. I'm not positive but looking at your
> > email
> >> > > > > address for your post it does not look to me like it is the
fake
> > one
> >> > > > > registered with MS. If they do not see the one that has been
> >> > registered with
> >> > > > > them then it is ignored. Note that this is not the email
address
> > that
> >> > the
> >> > > > > MSDN subscription has for you (i.e. it is NOT the passport
email
> >> > address,
> >> > > > > you have to specifically register an additional fake one that
is
> >> > > > > specifically for the managed newsgroup support).
> >> > > > >
> >> > > > > Go here:
> >> > > > > http://msdn.microsoft.com/newsgroups/managed/
> >> > > > >
> >> > > > > Login with passport
> >> > > > >
> >> > > > > Then scroll down to here:
> >> > > > > Getting Started
> >> > > > > The managed newsgroups are easy to use. Just follow these
simple
> >> > > > > instructions:
> >> > > > >
> >> > > > > a.. Register by creating your unique no-spam alias
> >> > > > > And click on the link.
> >> > > > >
> >> > > > > I didn't find it real intuitive about how it operates (first
> > posting,
> >> > using
> >> > > > > the alias)
> >> > > > >
> >> > > > >
> >> > > > > --
> >> > > > > Bruce Loehle-Conger
> >> > > > > MVP SQL Server Reporting Services
> >> > > > >
> >> > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in
> >> > > > > message
> >> > > > > news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
> >> > > > > >I am posting this through the "Managed NewsGroup"
> >> > > > > >
> >> >
> >
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> >> > > > > >
> >> > > > > > and am still not getting an answer. I also have an MSDN
> >> > subscription.
> >> > > > > > Based upon the above postings - shouldn't I get a response
> >> > > > > > back?
> >> > > > > >
> >> > > > > > The workaround will not work for me as we have almost a 1,000
> >> > reports that
> >> > > > > > get exported to Excel. Yes - we only notced this after SP1.
> >> > > > > >
> >> > > > > > It is obvious that this is a bug (a pretty big one at that).
I
> >> > don't want
> >> > > > > > to get into a "p*ss*ng contest" about this but am tired of
the
> > back
> >> > and
> >> > > > > > forth
> >> > > > > > about submitting a report case. It is simply a bug that is
> >> > relatively
> >> > > > > > simple
> >> > > > > > to reproduce.
> >> > > > > >
> >> > > > > >
> >> > > > > > "Bruce L-C [MVP]" wrote:
> >> > > > > >
> >> > > > > >> If you have universal you need to just post via a managed
> > newsgroup
> >> > (if
> >> > > > > >> you
> >> > > > > >> haven't done this you post with a special fake email address
> > that
> >> > you
> >> > > > > >> have
> >> > > > > >> registered in MSDN website and then someone from MS will
> >> > > > > >> answer
> > and
> >> > take
> >> > > > > >> your repro case.
> >> > > > > >>
> >> > > > > >> I still think you have a misconception about this newsgroup,
> > that
> >> > someone
> >> > > > > >> from MS is watching every thread and that there should be
some
> > sort
> >> > of
> >> > > > > >> official statement from them. That is not how it works. If
> > Brian
> >> > happens
> >> > > > > >> to
> >> > > > > >> stop by then he might do something with it. I noticed that
he
> > first
> >> > said
> >> > > > > >> the
> >> > > > > >> best thing was to get product support involved and then he
> > mentions
> >> > > > > >> posting.
> >> > > > > >> So he went both ways with his answer. Posting might get a
> > response,
> >> > with
> >> > > > > >> managed newsgroup or product support you will get a
response.
> >> > Otherwise
> >> > > > > >> it
> >> > > > > >> is peer.
> >> > > > > >> --
> >> > > > > >> Bruce Loehle-Conger
> >> > > > > >> MVP SQL Server Reporting Services
> >> > > > > >>
> >> > > > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in
> > message
> >> > > > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> >> > > > > >> > Read the whole thread, Brian Welcker said "you can post
it
> > here
> >> > but
> >> > > > > >> > for
> >> > > > > >> us
> >> > > > > >> > to repro, we would need more than a general problem
> > statement"
> >> > etc.
> >> > > > > >> > This
> >> > > > > >> is
> >> > > > > >> > exactly what I did way back (I found my old file and
posted
> > it
> >> > again).
> >> > > > > >> > The
> >> > > > > >> > same issue crops up, actually frequently, and an MS
employee
> > does
> >> > not
> >> > > > > >> > say
> >> > > > > >> > it's a bug, don't they know yet, or do they only tell
people
> > that
> >> > > > > >> > contact
> >> > > > > >> > the product support team?
> >> > > > > >> >
> >> > > > > >> > Our company has a universal MSDN subscription, and I am
not
> >> > hunting
> >> > > > > >> > this
> >> > > > > >> > issue, I bumped into the thread by accident, but could not
> > keep
> >> > quiet -
> >> > > > > >> > something walks and quacks like a duck.
> >> > > > > >> >
> >> > > > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
> > message
> >> > > > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> >> > > > > >> > > I just changed my view to see all messages and I then
see
> > that
> >> > this
> >> > > > > >> > > is a
> >> > > > > >> > > continuation of a posting from awhile back.
> >> > > > > >> > >
> >> > > > > >> > > It sounds like
> >> > > > > >> > > 1. you have a work around.
> >> > > > > >> > > 2. you want support from this newsgroup for your problem
> >> > > > > >> > > 3. you don't want to submit a support incident
> >> > > > > >> > >
> >> > > > > >> > > So, however much you feel like #2 should be happening
for
> > you,
> >> > that
> >> > > > > >> isn't
> >> > > > > >> > > how the newsgroup is setup to operate. You either need
to
> > open
> >> > an
> >> > > > > >> incident
> >> > > > > >> > > or have an msdn subscription. The only people that get
any
> >> > support
> >> > > > > >> > > other
> >> > > > > >> > > than peer support is if you are an MSDN subscription
> >> > > > > >> > > holder
> > in
> >> > which
> >> > > > > >> case
> >> > > > > >> > > you this newsgroup is part of the managed newsgroups.
> >> > > > > >> > >
> >> > > > > >> > >
> >> > > > > >> > > --
> >> > > > > >> > > Bruce Loehle-Conger
> >> > > > > >> > > MVP SQL Server Reporting Services
> >> > > > > >> > >
> >> > > > > >> > >
> >> > > > > >> > >
> >> > > > > >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote
> >> > > > > >> > > in
> >> > message
> >> > > > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> >> > > > > >> > > > If opening a support case would have fixed the problem
> > this
> >> > month,
> >> > > > > >> then
> >> > > > > >> > it
> >> > > > > >> > > > might have been worth the effort.
> >> > > > > >> > > > I posted this problem just after the release of SP1
> > (without
> >> > SP1
> >> > > > > >> > > > one
> >> > > > > >> > > cannot
> >> > > > > >> > > > export to Excel 2000), many others posted it since
then,
> > and
> >> > even
> >> > > > > >> > > > if I
> >> > > > > >> > > filed
> >> > > > > >> > > > an incident then, there is no such thing as SP2 yet,
and
> > the
> >> > client
> >> > > > > >> > would
> >> > > > > >> > > > have been off the roof by now.
> >> > > > > >> > > > What I don't understand is why the MS guys don't just
> > admit
> >> > that it
> >> > > > > >> > > > is
> >> > > > > >> a
> >> > > > > >> > > > problem and suggest a work-around or release a hot-fix
> >> > > > > >> > > > or
> >> > > > > >> > > > something.
> >> > > > > >> As
> >> > > > > >> > I
> >> > > > > >> > > > said, I found sizing the stuff above the table like
> > headers,
> >> > other
> >> > > > > >> text,
> >> > > > > >> > > > etc, fixes the problem (haven't had any complaints
from
> > the
> >> > > > > >> > > > client),
> >> > > > > >> and
> >> > > > > >> > > the
> >> > > > > >> > > > report that looses the last row, attached to my other
> >> > posting, was
> >> > > > > >> fixed
> >> > > > > >> > > > like this and is running at the client.
> >> > > > > >> > > >
> >> > > > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote
in
> >> > message
> >> > > > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> >> > > > > >> > > > > I suggest opening up a support case. If it is a bug
> >> > > > > >> > > > > you
> >> > don't get
> >> > > > > >> > > charged.
> >> > > > > >> > > > >
> >> > > > > >> > > > > --
> >> > > > > >> > > > > Bruce Loehle-Conger
> >> > > > > >> > > > > MVP SQL Server Reporting Services
> >> > > > > >> > > > >
> >> > > > > >> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> > wrote in
> >> > > > > >> > > > > message
> >> > > > > >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> >> > > > > >> > > > > > Hopefully by now you found a work-around, but in
> >> > > > > >> > > > > > case
> > you
> >> > did
> >> > > > > >> > > > > > not,
> >> > > > > >> I
> >> > > > > >> > > > found
> >> > > > > >> > > > > > that if I re-arrange the stuff above the table a
> > bit,
> >> > like
> >> > > > > >> headers
> >> > > > > >> > > and
> >> > > > > >> > > > > > other text, etc, it fixes the problem.
> >> > > > > >> > > > > >
> >> > > > > >> > > > > > "chanley54" <chanley54@.discussions.microsoft.com>
> > wrote
> >> > in
> >> > > > > >> > > > > > message
> >> > > > > >> > > > > >
> >> > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> >> > > > > >> > > > > > > Hello,
> >> > > > > >> > > > > > >
> >> > > > > >> > > > > > > This question has been posted a few times and is
> >> > DEFINITELY A
> >> > > > > >> SHOW
> >> > > > > >> > > > > STOPPER
> >> > > > > >> > > > > > > for Reporting Services.
> >> > > > > >> > > > > > >
> >> > > > > >> > > > > > > When exporting to Excel - the last row can turn
up
> >> > missing -
> >> > > > > >> > > > > > > Why
> >> > > > > >> > is
> >> > > > > >> > > > > > > Microsoft not responding to this?
> >> > > > > >> > > > > > >
> >> > > > > >> > > > > >
> >> > > > > >> > > > > >
> >> > > > > >> > > > >
> >> > > > > >> > > > >
> >> > > > > >> > > >
> >> > > > > >> > > >
> >> > > > > >> > >
> >> > > > > >> > >
> >> > > > > >> >
> >> > > > > >> >
> >> > > > > >>
> >> > > > > >>
> >> > > > > >>
> >> > > > >
> >> > > > >
> >> > > > >
> >> >
> >> >
> >> >
> >
> >
>|||This is a peer supported newsgroups unless you post (not add in a response
but start a post) using your managed newsgroup registered alias. If you do
that (and you have MSDN so you should be able to do this) then they will
answer you. Otherwise any MS posts are mostly people that jump on from time
to time but it is not their job to answer questions. They do this because
they want to.
If you have a support call that turns out to be a bug you are not charged. I
find it easier to use my managed newsgroup alias (I have two different
connections to this newsgroup) when I need an answer.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
news:%23GbmxMuCFHA.464@.TK2MSFTNGP15.phx.gbl...
> Brilliant! We obediently follow the procedures to get our posts noticed
by
> MS and... silence...
> Perhaps I should open a bug using our MSDN subscription instead...
> Thanks for the update and the ref to the bug list.
> "Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
> news:ONAxfOnCFHA.392@.TK2MSFTNGP14.phx.gbl...
> > Ever heard the story "The Emperor's new clothes", where the tailor said
> > that anybody that could not see the emperor's new clothes did not have
> good
> > taste, or something like that, while the emperor was actually naked?
This
> > issue reminds me of it. When I bumped into it for the 1st time just
after
> > SP1, one then eager MS guy said he would look into it, but must have
been
> > side tracked, or was told that there is no such bug, and since then,
every
> > so often, some desperate soul will post this issue, and then the MS guys
> > won't touch it. It is like say nothing, then there is nothing. I was
> > thinking that maybe it was the Chief of Reporting Services or someone
who
> > knows someone important, close to Bill maybe, programmed this part, and
> that
> > they are not allowed to tell.
> >
> > Just look down the newsgroup to a post on 1/29/2005 8:55 AM (5 days ago)
> by
> > "chanley54", titled "For MS Development Team - SP2", where he asked if
the
> > issue is fixed in SP2, silence from the MS camp.
> > The following link points to a list of bugs that are fixed by SP2 Beta,
> > dated 16 Dec 2004, and this issue is not mentioned there, however they
> > mention that "the list may be updated".
> > http://support.microsoft.com/default.aspx?scid=kb;en-us;889640
> >
> >
> > "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
> > news:OlA62DmCFHA.1432@.tk2msftngp13.phx.gbl...
> > > Last post was 12/7/2004... Any news from MS on this one - I just
bumped
> > > into the same wall with Excel 2003 and SP1...
> > >
> > > Cheers!
> > >
> > > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> > > news:26BF4F85-ED31-4DE7-9468-441B07976F2E@.microsoft.com...
> > >> Absolutely - I've got users breathing down my neck on this one.
> > >>
> > >> -- Chris
> > >>
> > >> "Chris Botha" wrote:
> > >>
> > >> > If this thing takes off on some other group or if you manage to get
a
> > >> > response from the MS guys, do you mind sending me an email?
> > >> > Thanks,
> > >> >
> > >> > Chris.
> > >> >
> > >> > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> > >> > news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
> > >> > > Bruce,
> > >> > >
> > >> > > Correction - I changed my alias and searched through the Managed
> > > NewsGroup
> > >> > > section and it brought me to the following:
> > >> > >
> > >> > >
> > >> >
> > >
>
http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
> > >> > >
> > >> > > Again - MS says that we will have a response in two day. Sorry
to
> > > beat
> > >> > this
> > >> > > to death.
> > >> > >
> > >> > > "chanley54" wrote:
> > >> > >
> > >> > > > Bruce,
> > >> > > >
> > >> > > > That's exactly what I have been doing. We do appricate the
help.
> > > This
> > >> > > > posting was made through the same process that you described.
> > >> > > >
> > >> > > > Perhaps I am doing something wrong but my return address shows
> the
> > >> > following:
> > >> > > > "chanley54@.discussions.microsoft.com"
> > >> > > >
> > >> > > > Regards.
> > >> > > >
> > >> > > >
> > >> > > > "Bruce L-C [MVP]" wrote:
> > >> > > >
> > >> > > > > I am trying to help you. Remember before attacking me that I
> help
> > >> > people
> > >> > > > > just for the hell of it. As such I am trying to let you know
> how
> > >> > things work
> > >> > > > > so you can successfully get your issue resolved.
> > >> > > > >
> > >> > > > > About managed newsgroups. There is no difference between this
> > >> > newsgroup and
> > >> > > > > a managed newsgroup. They are the same thing (whether you use
a
> > > web
> > >> > > > > interface or a outlook express). To have your posting to be
> > > included
> > >> > under
> > >> > > > > the managed newsgroup support terms (I believe it is within 2
> > > business
> > >> > days)
> > >> > > > > you have to do two things.
> > >> > > > > - you have to initiate the posting. The software they use to
> > > manage
> > >> > the
> > >> > > > > process only looks at whoever started the thread.
> > >> > > > > - the return email address has to be the fake one registered
as
> > > part
> > >> > of the
> > >> > > > > managed newsgroup process. I'm not positive but looking at
your
> > > email
> > >> > > > > address for your post it does not look to me like it is the
> fake
> > > one
> > >> > > > > registered with MS. If they do not see the one that has been
> > >> > registered with
> > >> > > > > them then it is ignored. Note that this is not the email
> address
> > > that
> > >> > the
> > >> > > > > MSDN subscription has for you (i.e. it is NOT the passport
> email
> > >> > address,
> > >> > > > > you have to specifically register an additional fake one that
> is
> > >> > > > > specifically for the managed newsgroup support).
> > >> > > > >
> > >> > > > > Go here:
> > >> > > > > http://msdn.microsoft.com/newsgroups/managed/
> > >> > > > >
> > >> > > > > Login with passport
> > >> > > > >
> > >> > > > > Then scroll down to here:
> > >> > > > > Getting Started
> > >> > > > > The managed newsgroups are easy to use. Just follow these
> simple
> > >> > > > > instructions:
> > >> > > > >
> > >> > > > > a.. Register by creating your unique no-spam alias
> > >> > > > > And click on the link.
> > >> > > > >
> > >> > > > > I didn't find it real intuitive about how it operates (first
> > > posting,
> > >> > using
> > >> > > > > the alias)
> > >> > > > >
> > >> > > > >
> > >> > > > > --
> > >> > > > > Bruce Loehle-Conger
> > >> > > > > MVP SQL Server Reporting Services
> > >> > > > >
> > >> > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in
> > >> > > > > message
> > >> > > > > news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
> > >> > > > > >I am posting this through the "Managed NewsGroup"
> > >> > > > > >
> > >> >
> > >
>
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> > >> > > > > >
> > >> > > > > > and am still not getting an answer. I also have an MSDN
> > >> > subscription.
> > >> > > > > > Based upon the above postings - shouldn't I get a response
> > >> > > > > > back?
> > >> > > > > >
> > >> > > > > > The workaround will not work for me as we have almost a
1,000
> > >> > reports that
> > >> > > > > > get exported to Excel. Yes - we only notced this after
SP1.
> > >> > > > > >
> > >> > > > > > It is obvious that this is a bug (a pretty big one at
that).
> I
> > >> > don't want
> > >> > > > > > to get into a "p*ss*ng contest" about this but am tired of
> the
> > > back
> > >> > and
> > >> > > > > > forth
> > >> > > > > > about submitting a report case. It is simply a bug that is
> > >> > relatively
> > >> > > > > > simple
> > >> > > > > > to reproduce.
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > "Bruce L-C [MVP]" wrote:
> > >> > > > > >
> > >> > > > > >> If you have universal you need to just post via a managed
> > > newsgroup
> > >> > (if
> > >> > > > > >> you
> > >> > > > > >> haven't done this you post with a special fake email
address
> > > that
> > >> > you
> > >> > > > > >> have
> > >> > > > > >> registered in MSDN website and then someone from MS will
> > >> > > > > >> answer
> > > and
> > >> > take
> > >> > > > > >> your repro case.
> > >> > > > > >>
> > >> > > > > >> I still think you have a misconception about this
newsgroup,
> > > that
> > >> > someone
> > >> > > > > >> from MS is watching every thread and that there should be
> some
> > > sort
> > >> > of
> > >> > > > > >> official statement from them. That is not how it works. If
> > > Brian
> > >> > happens
> > >> > > > > >> to
> > >> > > > > >> stop by then he might do something with it. I noticed that
> he
> > > first
> > >> > said
> > >> > > > > >> the
> > >> > > > > >> best thing was to get product support involved and then he
> > > mentions
> > >> > > > > >> posting.
> > >> > > > > >> So he went both ways with his answer. Posting might get a
> > > response,
> > >> > with
> > >> > > > > >> managed newsgroup or product support you will get a
> response.
> > >> > Otherwise
> > >> > > > > >> it
> > >> > > > > >> is peer.
> > >> > > > > >> --
> > >> > > > > >> Bruce Loehle-Conger
> > >> > > > > >> MVP SQL Server Reporting Services
> > >> > > > > >>
> > >> > > > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote
in
> > > message
> > >> > > > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> > >> > > > > >> > Read the whole thread, Brian Welcker said "you can post
> it
> > > here
> > >> > but
> > >> > > > > >> > for
> > >> > > > > >> us
> > >> > > > > >> > to repro, we would need more than a general problem
> > > statement"
> > >> > etc.
> > >> > > > > >> > This
> > >> > > > > >> is
> > >> > > > > >> > exactly what I did way back (I found my old file and
> posted
> > > it
> > >> > again).
> > >> > > > > >> > The
> > >> > > > > >> > same issue crops up, actually frequently, and an MS
> employee
> > > does
> > >> > not
> > >> > > > > >> > say
> > >> > > > > >> > it's a bug, don't they know yet, or do they only tell
> people
> > > that
> > >> > > > > >> > contact
> > >> > > > > >> > the product support team?
> > >> > > > > >> >
> > >> > > > > >> > Our company has a universal MSDN subscription, and I am
> not
> > >> > hunting
> > >> > > > > >> > this
> > >> > > > > >> > issue, I bumped into the thread by accident, but could
not
> > > keep
> > >> > quiet -
> > >> > > > > >> > something walks and quacks like a duck.
> > >> > > > > >> >
> > >> > > > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
> > > message
> > >> > > > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> > >> > > > > >> > > I just changed my view to see all messages and I then
> see
> > > that
> > >> > this
> > >> > > > > >> > > is a
> > >> > > > > >> > > continuation of a posting from awhile back.
> > >> > > > > >> > >
> > >> > > > > >> > > It sounds like
> > >> > > > > >> > > 1. you have a work around.
> > >> > > > > >> > > 2. you want support from this newsgroup for your
problem
> > >> > > > > >> > > 3. you don't want to submit a support incident
> > >> > > > > >> > >
> > >> > > > > >> > > So, however much you feel like #2 should be happening
> for
> > > you,
> > >> > that
> > >> > > > > >> isn't
> > >> > > > > >> > > how the newsgroup is setup to operate. You either need
> to
> > > open
> > >> > an
> > >> > > > > >> incident
> > >> > > > > >> > > or have an msdn subscription. The only people that get
> any
> > >> > support
> > >> > > > > >> > > other
> > >> > > > > >> > > than peer support is if you are an MSDN subscription
> > >> > > > > >> > > holder
> > > in
> > >> > which
> > >> > > > > >> case
> > >> > > > > >> > > you this newsgroup is part of the managed newsgroups.
> > >> > > > > >> > >
> > >> > > > > >> > >
> > >> > > > > >> > > --
> > >> > > > > >> > > Bruce Loehle-Conger
> > >> > > > > >> > > MVP SQL Server Reporting Services
> > >> > > > > >> > >
> > >> > > > > >> > >
> > >> > > > > >> > >
> > >> > > > > >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
wrote
> > >> > > > > >> > > in
> > >> > message
> > >> > > > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> > >> > > > > >> > > > If opening a support case would have fixed the
problem
> > > this
> > >> > month,
> > >> > > > > >> then
> > >> > > > > >> > it
> > >> > > > > >> > > > might have been worth the effort.
> > >> > > > > >> > > > I posted this problem just after the release of SP1
> > > (without
> > >> > SP1
> > >> > > > > >> > > > one
> > >> > > > > >> > > cannot
> > >> > > > > >> > > > export to Excel 2000), many others posted it since
> then,
> > > and
> > >> > even
> > >> > > > > >> > > > if I
> > >> > > > > >> > > filed
> > >> > > > > >> > > > an incident then, there is no such thing as SP2 yet,
> and
> > > the
> > >> > client
> > >> > > > > >> > would
> > >> > > > > >> > > > have been off the roof by now.
> > >> > > > > >> > > > What I don't understand is why the MS guys don't
just
> > > admit
> > >> > that it
> > >> > > > > >> > > > is
> > >> > > > > >> a
> > >> > > > > >> > > > problem and suggest a work-around or release a
hot-fix
> > >> > > > > >> > > > or
> > >> > > > > >> > > > something.
> > >> > > > > >> As
> > >> > > > > >> > I
> > >> > > > > >> > > > said, I found sizing the stuff above the table like
> > > headers,
> > >> > other
> > >> > > > > >> text,
> > >> > > > > >> > > > etc, fixes the problem (haven't had any complaints
> from
> > > the
> > >> > > > > >> > > > client),
> > >> > > > > >> and
> > >> > > > > >> > > the
> > >> > > > > >> > > > report that looses the last row, attached to my
other
> > >> > posting, was
> > >> > > > > >> fixed
> > >> > > > > >> > > > like this and is running at the client.
> > >> > > > > >> > > >
> > >> > > > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote
> in
> > >> > message
> > >> > > > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > >> > > > > >> > > > > I suggest opening up a support case. If it is a
bug
> > >> > > > > >> > > > > you
> > >> > don't get
> > >> > > > > >> > > charged.
> > >> > > > > >> > > > >
> > >> > > > > >> > > > > --
> > >> > > > > >> > > > > Bruce Loehle-Conger
> > >> > > > > >> > > > > MVP SQL Server Reporting Services
> > >> > > > > >> > > > >
> > >> > > > > >> > > > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> > > wrote in
> > >> > > > > >> > > > > message
> > >> > > > > >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > >> > > > > >> > > > > > Hopefully by now you found a work-around, but in
> > >> > > > > >> > > > > > case
> > > you
> > >> > did
> > >> > > > > >> > > > > > not,
> > >> > > > > >> I
> > >> > > > > >> > > > found
> > >> > > > > >> > > > > > that if I re-arrange the stuff above the table
a
> > > bit,
> > >> > like
> > >> > > > > >> headers
> > >> > > > > >> > > and
> > >> > > > > >> > > > > > other text, etc, it fixes the problem.
> > >> > > > > >> > > > > >
> > >> > > > > >> > > > > > "chanley54"
<chanley54@.discussions.microsoft.com>
> > > wrote
> > >> > in
> > >> > > > > >> > > > > > message
> > >> > > > > >> > > > > >
> > >> > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > >> > > > > >> > > > > > > Hello,
> > >> > > > > >> > > > > > >
> > >> > > > > >> > > > > > > This question has been posted a few times and
is
> > >> > DEFINITELY A
> > >> > > > > >> SHOW
> > >> > > > > >> > > > > STOPPER
> > >> > > > > >> > > > > > > for Reporting Services.
> > >> > > > > >> > > > > > >
> > >> > > > > >> > > > > > > When exporting to Excel - the last row can
turn
> up
> > >> > missing -
> > >> > > > > >> > > > > > > Why
> > >> > > > > >> > is
> > >> > > > > >> > > > > > > Microsoft not responding to this?
> > >> > > > > >> > > > > > >
> > >> > > > > >> > > > > >
> > >> > > > > >> > > > > >
> > >> > > > > >> > > > >
> > >> > > > > >> > > > >
> > >> > > > > >> > > >
> > >> > > > > >> > > >
> > >> > > > > >> > >
> > >> > > > > >> > >
> > >> > > > > >> >
> > >> > > > > >> >
> > >> > > > > >>
> > >> > > > > >>
> > >> > > > > >>
> > >> > > > >
> > >> > > > >
> > >> > > > >
> > >> >
> > >> >
> > >> >
> > >
> > >
> >
> >
>|||They obviously "don't want to" touch this one. Can you tell me what the
steps are to get a "managed newsgroup registered alias", or point me to a
page where the information is? We are a MSDN Universal subscriber. I will
then start a thread for this issue and see if I can lure them in. Thanks.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:O$buPUuCFHA.3504@.TK2MSFTNGP12.phx.gbl...
> This is a peer supported newsgroups unless you post (not add in a response
> but start a post) using your managed newsgroup registered alias. If you do
> that (and you have MSDN so you should be able to do this) then they will
> answer you. Otherwise any MS posts are mostly people that jump on from
> time
> to time but it is not their job to answer questions. They do this because
> they want to.
> If you have a support call that turns out to be a bug you are not charged.
> I
> find it easier to use my managed newsgroup alias (I have two different
> connections to this newsgroup) when I need an answer.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
> news:%23GbmxMuCFHA.464@.TK2MSFTNGP15.phx.gbl...
>> Brilliant! We obediently follow the procedures to get our posts noticed
> by
>> MS and... silence...
>> Perhaps I should open a bug using our MSDN subscription instead...
>> Thanks for the update and the ref to the bug list.
>> "Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
>> news:ONAxfOnCFHA.392@.TK2MSFTNGP14.phx.gbl...
>> > Ever heard the story "The Emperor's new clothes", where the tailor
>> > said
>> > that anybody that could not see the emperor's new clothes did not have
>> good
>> > taste, or something like that, while the emperor was actually naked?
> This
>> > issue reminds me of it. When I bumped into it for the 1st time just
> after
>> > SP1, one then eager MS guy said he would look into it, but must have
> been
>> > side tracked, or was told that there is no such bug, and since then,
> every
>> > so often, some desperate soul will post this issue, and then the MS
>> > guys
>> > won't touch it. It is like say nothing, then there is nothing. I was
>> > thinking that maybe it was the Chief of Reporting Services or someone
> who
>> > knows someone important, close to Bill maybe, programmed this part, and
>> that
>> > they are not allowed to tell.
>> >
>> > Just look down the newsgroup to a post on 1/29/2005 8:55 AM (5 days
>> > ago)
>> by
>> > "chanley54", titled "For MS Development Team - SP2", where he asked if
> the
>> > issue is fixed in SP2, silence from the MS camp.
>> > The following link points to a list of bugs that are fixed by SP2 Beta,
>> > dated 16 Dec 2004, and this issue is not mentioned there, however they
>> > mention that "the list may be updated".
>> > http://support.microsoft.com/default.aspx?scid=kb;en-us;889640
>> >
>> >
>> > "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
>> > news:OlA62DmCFHA.1432@.tk2msftngp13.phx.gbl...
>> > > Last post was 12/7/2004... Any news from MS on this one - I just
> bumped
>> > > into the same wall with Excel 2003 and SP1...
>> > >
>> > > Cheers!
>> > >
>> > > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
>> > > news:26BF4F85-ED31-4DE7-9468-441B07976F2E@.microsoft.com...
>> > >> Absolutely - I've got users breathing down my neck on this one.
>> > >>
>> > >> -- Chris
>> > >>
>> > >> "Chris Botha" wrote:
>> > >>
>> > >> > If this thing takes off on some other group or if you manage to
>> > >> > get
> a
>> > >> > response from the MS guys, do you mind sending me an email?
>> > >> > Thanks,
>> > >> >
>> > >> > Chris.
>> > >> >
>> > >> > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
>> > >> > news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
>> > >> > > Bruce,
>> > >> > >
>> > >> > > Correction - I changed my alias and searched through the Managed
>> > > NewsGroup
>> > >> > > section and it brought me to the following:
>> > >> > >
>> > >> > >
>> > >> >
>> > >
> http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
>> > >> > >
>> > >> > > Again - MS says that we will have a response in two day. Sorry
> to
>> > > beat
>> > >> > this
>> > >> > > to death.
>> > >> > >
>> > >> > > "chanley54" wrote:
>> > >> > >
>> > >> > > > Bruce,
>> > >> > > >
>> > >> > > > That's exactly what I have been doing. We do appricate the
> help.
>> > > This
>> > >> > > > posting was made through the same process that you described.
>> > >> > > >
>> > >> > > > Perhaps I am doing something wrong but my return address shows
>> the
>> > >> > following:
>> > >> > > > "chanley54@.discussions.microsoft.com"
>> > >> > > >
>> > >> > > > Regards.
>> > >> > > >
>> > >> > > >
>> > >> > > > "Bruce L-C [MVP]" wrote:
>> > >> > > >
>> > >> > > > > I am trying to help you. Remember before attacking me that I
>> help
>> > >> > people
>> > >> > > > > just for the hell of it. As such I am trying to let you know
>> how
>> > >> > things work
>> > >> > > > > so you can successfully get your issue resolved.
>> > >> > > > >
>> > >> > > > > About managed newsgroups. There is no difference between
>> > >> > > > > this
>> > >> > newsgroup and
>> > >> > > > > a managed newsgroup. They are the same thing (whether you
>> > >> > > > > use
> a
>> > > web
>> > >> > > > > interface or a outlook express). To have your posting to be
>> > > included
>> > >> > under
>> > >> > > > > the managed newsgroup support terms (I believe it is within
>> > >> > > > > 2
>> > > business
>> > >> > days)
>> > >> > > > > you have to do two things.
>> > >> > > > > - you have to initiate the posting. The software they use to
>> > > manage
>> > >> > the
>> > >> > > > > process only looks at whoever started the thread.
>> > >> > > > > - the return email address has to be the fake one registered
> as
>> > > part
>> > >> > of the
>> > >> > > > > managed newsgroup process. I'm not positive but looking at
> your
>> > > email
>> > >> > > > > address for your post it does not look to me like it is the
>> fake
>> > > one
>> > >> > > > > registered with MS. If they do not see the one that has been
>> > >> > registered with
>> > >> > > > > them then it is ignored. Note that this is not the email
>> address
>> > > that
>> > >> > the
>> > >> > > > > MSDN subscription has for you (i.e. it is NOT the passport
>> email
>> > >> > address,
>> > >> > > > > you have to specifically register an additional fake one
>> > >> > > > > that
>> is
>> > >> > > > > specifically for the managed newsgroup support).
>> > >> > > > >
>> > >> > > > > Go here:
>> > >> > > > > http://msdn.microsoft.com/newsgroups/managed/
>> > >> > > > >
>> > >> > > > > Login with passport
>> > >> > > > >
>> > >> > > > > Then scroll down to here:
>> > >> > > > > Getting Started
>> > >> > > > > The managed newsgroups are easy to use. Just follow these
>> simple
>> > >> > > > > instructions:
>> > >> > > > >
>> > >> > > > > a.. Register by creating your unique no-spam alias
>> > >> > > > > And click on the link.
>> > >> > > > >
>> > >> > > > > I didn't find it real intuitive about how it operates (first
>> > > posting,
>> > >> > using
>> > >> > > > > the alias)
>> > >> > > > >
>> > >> > > > >
>> > >> > > > > --
>> > >> > > > > Bruce Loehle-Conger
>> > >> > > > > MVP SQL Server Reporting Services
>> > >> > > > >
>> > >> > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in
>> > >> > > > > message
>> > >> > > > > news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
>> > >> > > > > >I am posting this through the "Managed NewsGroup"
>> > >> > > > > >
>> > >> >
>> > >
> http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
>> > >> > > > > >
>> > >> > > > > > and am still not getting an answer. I also have an MSDN
>> > >> > subscription.
>> > >> > > > > > Based upon the above postings - shouldn't I get a response
>> > >> > > > > > back?
>> > >> > > > > >
>> > >> > > > > > The workaround will not work for me as we have almost a
> 1,000
>> > >> > reports that
>> > >> > > > > > get exported to Excel. Yes - we only notced this after
> SP1.
>> > >> > > > > >
>> > >> > > > > > It is obvious that this is a bug (a pretty big one at
> that).
>> I
>> > >> > don't want
>> > >> > > > > > to get into a "p*ss*ng contest" about this but am tired of
>> the
>> > > back
>> > >> > and
>> > >> > > > > > forth
>> > >> > > > > > about submitting a report case. It is simply a bug that
>> > >> > > > > > is
>> > >> > relatively
>> > >> > > > > > simple
>> > >> > > > > > to reproduce.
>> > >> > > > > >
>> > >> > > > > >
>> > >> > > > > > "Bruce L-C [MVP]" wrote:
>> > >> > > > > >
>> > >> > > > > >> If you have universal you need to just post via a managed
>> > > newsgroup
>> > >> > (if
>> > >> > > > > >> you
>> > >> > > > > >> haven't done this you post with a special fake email
> address
>> > > that
>> > >> > you
>> > >> > > > > >> have
>> > >> > > > > >> registered in MSDN website and then someone from MS will
>> > >> > > > > >> answer
>> > > and
>> > >> > take
>> > >> > > > > >> your repro case.
>> > >> > > > > >>
>> > >> > > > > >> I still think you have a misconception about this
> newsgroup,
>> > > that
>> > >> > someone
>> > >> > > > > >> from MS is watching every thread and that there should be
>> some
>> > > sort
>> > >> > of
>> > >> > > > > >> official statement from them. That is not how it works.
>> > >> > > > > >> If
>> > > Brian
>> > >> > happens
>> > >> > > > > >> to
>> > >> > > > > >> stop by then he might do something with it. I noticed
>> > >> > > > > >> that
>> he
>> > > first
>> > >> > said
>> > >> > > > > >> the
>> > >> > > > > >> best thing was to get product support involved and then
>> > >> > > > > >> he
>> > > mentions
>> > >> > > > > >> posting.
>> > >> > > > > >> So he went both ways with his answer. Posting might get a
>> > > response,
>> > >> > with
>> > >> > > > > >> managed newsgroup or product support you will get a
>> response.
>> > >> > Otherwise
>> > >> > > > > >> it
>> > >> > > > > >> is peer.
>> > >> > > > > >> --
>> > >> > > > > >> Bruce Loehle-Conger
>> > >> > > > > >> MVP SQL Server Reporting Services
>> > >> > > > > >>
>> > >> > > > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote
> in
>> > > message
>> > >> > > > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
>> > >> > > > > >> > Read the whole thread, Brian Welcker said "you can
>> > >> > > > > >> > post
>> it
>> > > here
>> > >> > but
>> > >> > > > > >> > for
>> > >> > > > > >> us
>> > >> > > > > >> > to repro, we would need more than a general problem
>> > > statement"
>> > >> > etc.
>> > >> > > > > >> > This
>> > >> > > > > >> is
>> > >> > > > > >> > exactly what I did way back (I found my old file and
>> posted
>> > > it
>> > >> > again).
>> > >> > > > > >> > The
>> > >> > > > > >> > same issue crops up, actually frequently, and an MS
>> employee
>> > > does
>> > >> > not
>> > >> > > > > >> > say
>> > >> > > > > >> > it's a bug, don't they know yet, or do they only tell
>> people
>> > > that
>> > >> > > > > >> > contact
>> > >> > > > > >> > the product support team?
>> > >> > > > > >> >
>> > >> > > > > >> > Our company has a universal MSDN subscription, and I am
>> not
>> > >> > hunting
>> > >> > > > > >> > this
>> > >> > > > > >> > issue, I bumped into the thread by accident, but could
> not
>> > > keep
>> > >> > quiet -
>> > >> > > > > >> > something walks and quacks like a duck.
>> > >> > > > > >> >
>> > >> > > > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
>> > > message
>> > >> > > > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
>> > >> > > > > >> > > I just changed my view to see all messages and I then
>> see
>> > > that
>> > >> > this
>> > >> > > > > >> > > is a
>> > >> > > > > >> > > continuation of a posting from awhile back.
>> > >> > > > > >> > >
>> > >> > > > > >> > > It sounds like
>> > >> > > > > >> > > 1. you have a work around.
>> > >> > > > > >> > > 2. you want support from this newsgroup for your
> problem
>> > >> > > > > >> > > 3. you don't want to submit a support incident
>> > >> > > > > >> > >
>> > >> > > > > >> > > So, however much you feel like #2 should be happening
>> for
>> > > you,
>> > >> > that
>> > >> > > > > >> isn't
>> > >> > > > > >> > > how the newsgroup is setup to operate. You either
>> > >> > > > > >> > > need
>> to
>> > > open
>> > >> > an
>> > >> > > > > >> incident
>> > >> > > > > >> > > or have an msdn subscription. The only people that
>> > >> > > > > >> > > get
>> any
>> > >> > support
>> > >> > > > > >> > > other
>> > >> > > > > >> > > than peer support is if you are an MSDN subscription
>> > >> > > > > >> > > holder
>> > > in
>> > >> > which
>> > >> > > > > >> case
>> > >> > > > > >> > > you this newsgroup is part of the managed newsgroups.
>> > >> > > > > >> > >
>> > >> > > > > >> > >
>> > >> > > > > >> > > --
>> > >> > > > > >> > > Bruce Loehle-Conger
>> > >> > > > > >> > > MVP SQL Server Reporting Services
>> > >> > > > > >> > >
>> > >> > > > > >> > >
>> > >> > > > > >> > >
>> > >> > > > > >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> wrote
>> > >> > > > > >> > > in
>> > >> > message
>> > >> > > > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
>> > >> > > > > >> > > > If opening a support case would have fixed the
> problem
>> > > this
>> > >> > month,
>> > >> > > > > >> then
>> > >> > > > > >> > it
>> > >> > > > > >> > > > might have been worth the effort.
>> > >> > > > > >> > > > I posted this problem just after the release of SP1
>> > > (without
>> > >> > SP1
>> > >> > > > > >> > > > one
>> > >> > > > > >> > > cannot
>> > >> > > > > >> > > > export to Excel 2000), many others posted it since
>> then,
>> > > and
>> > >> > even
>> > >> > > > > >> > > > if I
>> > >> > > > > >> > > filed
>> > >> > > > > >> > > > an incident then, there is no such thing as SP2
>> > >> > > > > >> > > > yet,
>> and
>> > > the
>> > >> > client
>> > >> > > > > >> > would
>> > >> > > > > >> > > > have been off the roof by now.
>> > >> > > > > >> > > > What I don't understand is why the MS guys don't
> just
>> > > admit
>> > >> > that it
>> > >> > > > > >> > > > is
>> > >> > > > > >> a
>> > >> > > > > >> > > > problem and suggest a work-around or release a
> hot-fix
>> > >> > > > > >> > > > or
>> > >> > > > > >> > > > something.
>> > >> > > > > >> As
>> > >> > > > > >> > I
>> > >> > > > > >> > > > said, I found sizing the stuff above the table like
>> > > headers,
>> > >> > other
>> > >> > > > > >> text,
>> > >> > > > > >> > > > etc, fixes the problem (haven't had any complaints
>> from
>> > > the
>> > >> > > > > >> > > > client),
>> > >> > > > > >> and
>> > >> > > > > >> > > the
>> > >> > > > > >> > > > report that looses the last row, attached to my
> other
>> > >> > posting, was
>> > >> > > > > >> fixed
>> > >> > > > > >> > > > like this and is running at the client.
>> > >> > > > > >> > > >
>> > >> > > > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com>
>> > >> > > > > >> > > > wrote
>> in
>> > >> > message
>> > >> > > > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
>> > >> > > > > >> > > > > I suggest opening up a support case. If it is a
> bug
>> > >> > > > > >> > > > > you
>> > >> > don't get
>> > >> > > > > >> > > charged.
>> > >> > > > > >> > > > >
>> > >> > > > > >> > > > > --
>> > >> > > > > >> > > > > Bruce Loehle-Conger
>> > >> > > > > >> > > > > MVP SQL Server Reporting Services
>> > >> > > > > >> > > > >
>> > >> > > > > >> > > > > "Chris Botha"
>> > >> > > > > >> > > > > <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
>> > > wrote in
>> > >> > > > > >> > > > > message
>> > >> > > > > >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
>> > >> > > > > >> > > > > > Hopefully by now you found a work-around, but
>> > >> > > > > >> > > > > > in
>> > >> > > > > >> > > > > > case
>> > > you
>> > >> > did
>> > >> > > > > >> > > > > > not,
>> > >> > > > > >> I
>> > >> > > > > >> > > > found
>> > >> > > > > >> > > > > > that if I re-arrange the stuff above the table
> a
>> > > bit,
>> > >> > like
>> > >> > > > > >> headers
>> > >> > > > > >> > > and
>> > >> > > > > >> > > > > > other text, etc, it fixes the problem.
>> > >> > > > > >> > > > > >
>> > >> > > > > >> > > > > > "chanley54"
> <chanley54@.discussions.microsoft.com>
>> > > wrote
>> > >> > in
>> > >> > > > > >> > > > > > message
>> > >> > > > > >> > > > > >
>> > >> > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
>> > >> > > > > >> > > > > > > Hello,
>> > >> > > > > >> > > > > > >
>> > >> > > > > >> > > > > > > This question has been posted a few times and
> is
>> > >> > DEFINITELY A
>> > >> > > > > >> SHOW
>> > >> > > > > >> > > > > STOPPER
>> > >> > > > > >> > > > > > > for Reporting Services.
>> > >> > > > > >> > > > > > >
>> > >> > > > > >> > > > > > > When exporting to Excel - the last row can
> turn
>> up
>> > >> > missing -
>> > >> > > > > >> > > > > > > Why
>> > >> > > > > >> > is
>> > >> > > > > >> > > > > > > Microsoft not responding to this?
>> > >> > > > > >> > > > > > >
>> > >> > > > > >> > > > > >
>> > >> > > > > >> > > > > >
>> > >> > > > > >> > > > >
>> > >> > > > > >> > > > >
>> > >> > > > > >> > > >
>> > >> > > > > >> > > >
>> > >> > > > > >> > >
>> > >> > > > > >> > >
>> > >> > > > > >> >
>> > >> > > > > >> >
>> > >> > > > > >>
>> > >> > > > > >>
>> > >> > > > > >>
>> > >> > > > >
>> > >> > > > >
>> > >> > > > >
>> > >> >
>> > >> >
>> > >> >
>> > >
>> > >
>> >
>> >
>>
>|||This explains all about it.
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
news:e%23z9okuCFHA.4004@.tk2msftngp13.phx.gbl...
> They obviously "don't want to" touch this one. Can you tell me what the
> steps are to get a "managed newsgroup registered alias", or point me to a
> page where the information is? We are a MSDN Universal subscriber. I will
> then start a thread for this issue and see if I can lure them in. Thanks.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:O$buPUuCFHA.3504@.TK2MSFTNGP12.phx.gbl...
> > This is a peer supported newsgroups unless you post (not add in a
response
> > but start a post) using your managed newsgroup registered alias. If you
do
> > that (and you have MSDN so you should be able to do this) then they will
> > answer you. Otherwise any MS posts are mostly people that jump on from
> > time
> > to time but it is not their job to answer questions. They do this
because
> > they want to.
> >
> > If you have a support call that turns out to be a bug you are not
charged.
> > I
> > find it easier to use my managed newsgroup alias (I have two different
> > connections to this newsgroup) when I need an answer.
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
> > news:%23GbmxMuCFHA.464@.TK2MSFTNGP15.phx.gbl...
> >> Brilliant! We obediently follow the procedures to get our posts
noticed
> > by
> >> MS and... silence...
> >>
> >> Perhaps I should open a bug using our MSDN subscription instead...
> >>
> >> Thanks for the update and the ref to the bug list.
> >>
> >> "Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
> >> news:ONAxfOnCFHA.392@.TK2MSFTNGP14.phx.gbl...
> >> > Ever heard the story "The Emperor's new clothes", where the tailor
> >> > said
> >> > that anybody that could not see the emperor's new clothes did not
have
> >> good
> >> > taste, or something like that, while the emperor was actually naked?
> > This
> >> > issue reminds me of it. When I bumped into it for the 1st time just
> > after
> >> > SP1, one then eager MS guy said he would look into it, but must have
> > been
> >> > side tracked, or was told that there is no such bug, and since then,
> > every
> >> > so often, some desperate soul will post this issue, and then the MS
> >> > guys
> >> > won't touch it. It is like say nothing, then there is nothing. I was
> >> > thinking that maybe it was the Chief of Reporting Services or someone
> > who
> >> > knows someone important, close to Bill maybe, programmed this part,
and
> >> that
> >> > they are not allowed to tell.
> >> >
> >> > Just look down the newsgroup to a post on 1/29/2005 8:55 AM (5 days
> >> > ago)
> >> by
> >> > "chanley54", titled "For MS Development Team - SP2", where he asked
if
> > the
> >> > issue is fixed in SP2, silence from the MS camp.
> >> > The following link points to a list of bugs that are fixed by SP2
Beta,
> >> > dated 16 Dec 2004, and this issue is not mentioned there, however
they
> >> > mention that "the list may be updated".
> >> > http://support.microsoft.com/default.aspx?scid=kb;en-us;889640
> >> >
> >> >
> >> > "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
> >> > news:OlA62DmCFHA.1432@.tk2msftngp13.phx.gbl...
> >> > > Last post was 12/7/2004... Any news from MS on this one - I just
> > bumped
> >> > > into the same wall with Excel 2003 and SP1...
> >> > >
> >> > > Cheers!
> >> > >
> >> > > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> >> > > news:26BF4F85-ED31-4DE7-9468-441B07976F2E@.microsoft.com...
> >> > >> Absolutely - I've got users breathing down my neck on this one.
> >> > >>
> >> > >> -- Chris
> >> > >>
> >> > >> "Chris Botha" wrote:
> >> > >>
> >> > >> > If this thing takes off on some other group or if you manage to
> >> > >> > get
> > a
> >> > >> > response from the MS guys, do you mind sending me an email?
> >> > >> > Thanks,
> >> > >> >
> >> > >> > Chris.
> >> > >> >
> >> > >> > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> >> > >> > news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
> >> > >> > > Bruce,
> >> > >> > >
> >> > >> > > Correction - I changed my alias and searched through the
Managed
> >> > > NewsGroup
> >> > >> > > section and it brought me to the following:
> >> > >> > >
> >> > >> > >
> >> > >> >
> >> > >
> >>
> >
http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
> >> > >> > >
> >> > >> > > Again - MS says that we will have a response in two day.
Sorry
> > to
> >> > > beat
> >> > >> > this
> >> > >> > > to death.
> >> > >> > >
> >> > >> > > "chanley54" wrote:
> >> > >> > >
> >> > >> > > > Bruce,
> >> > >> > > >
> >> > >> > > > That's exactly what I have been doing. We do appricate the
> > help.
> >> > > This
> >> > >> > > > posting was made through the same process that you
described.
> >> > >> > > >
> >> > >> > > > Perhaps I am doing something wrong but my return address
shows
> >> the
> >> > >> > following:
> >> > >> > > > "chanley54@.discussions.microsoft.com"
> >> > >> > > >
> >> > >> > > > Regards.
> >> > >> > > >
> >> > >> > > >
> >> > >> > > > "Bruce L-C [MVP]" wrote:
> >> > >> > > >
> >> > >> > > > > I am trying to help you. Remember before attacking me that
I
> >> help
> >> > >> > people
> >> > >> > > > > just for the hell of it. As such I am trying to let you
know
> >> how
> >> > >> > things work
> >> > >> > > > > so you can successfully get your issue resolved.
> >> > >> > > > >
> >> > >> > > > > About managed newsgroups. There is no difference between
> >> > >> > > > > this
> >> > >> > newsgroup and
> >> > >> > > > > a managed newsgroup. They are the same thing (whether you
> >> > >> > > > > use
> > a
> >> > > web
> >> > >> > > > > interface or a outlook express). To have your posting to
be
> >> > > included
> >> > >> > under
> >> > >> > > > > the managed newsgroup support terms (I believe it is
within
> >> > >> > > > > 2
> >> > > business
> >> > >> > days)
> >> > >> > > > > you have to do two things.
> >> > >> > > > > - you have to initiate the posting. The software they use
to
> >> > > manage
> >> > >> > the
> >> > >> > > > > process only looks at whoever started the thread.
> >> > >> > > > > - the return email address has to be the fake one
registered
> > as
> >> > > part
> >> > >> > of the
> >> > >> > > > > managed newsgroup process. I'm not positive but looking at
> > your
> >> > > email
> >> > >> > > > > address for your post it does not look to me like it is
the
> >> fake
> >> > > one
> >> > >> > > > > registered with MS. If they do not see the one that has
been
> >> > >> > registered with
> >> > >> > > > > them then it is ignored. Note that this is not the email
> >> address
> >> > > that
> >> > >> > the
> >> > >> > > > > MSDN subscription has for you (i.e. it is NOT the passport
> >> email
> >> > >> > address,
> >> > >> > > > > you have to specifically register an additional fake one
> >> > >> > > > > that
> >> is
> >> > >> > > > > specifically for the managed newsgroup support).
> >> > >> > > > >
> >> > >> > > > > Go here:
> >> > >> > > > > http://msdn.microsoft.com/newsgroups/managed/
> >> > >> > > > >
> >> > >> > > > > Login with passport
> >> > >> > > > >
> >> > >> > > > > Then scroll down to here:
> >> > >> > > > > Getting Started
> >> > >> > > > > The managed newsgroups are easy to use. Just follow these
> >> simple
> >> > >> > > > > instructions:
> >> > >> > > > >
> >> > >> > > > > a.. Register by creating your unique no-spam alias
> >> > >> > > > > And click on the link.
> >> > >> > > > >
> >> > >> > > > > I didn't find it real intuitive about how it operates
(first
> >> > > posting,
> >> > >> > using
> >> > >> > > > > the alias)
> >> > >> > > > >
> >> > >> > > > >
> >> > >> > > > > --
> >> > >> > > > > Bruce Loehle-Conger
> >> > >> > > > > MVP SQL Server Reporting Services
> >> > >> > > > >
> >> > >> > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in
> >> > >> > > > > message
> >> > >> > > > > news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
> >> > >> > > > > >I am posting this through the "Managed NewsGroup"
> >> > >> > > > > >
> >> > >> >
> >> > >
> >>
> >
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> >> > >> > > > > >
> >> > >> > > > > > and am still not getting an answer. I also have an MSDN
> >> > >> > subscription.
> >> > >> > > > > > Based upon the above postings - shouldn't I get a
response
> >> > >> > > > > > back?
> >> > >> > > > > >
> >> > >> > > > > > The workaround will not work for me as we have almost a
> > 1,000
> >> > >> > reports that
> >> > >> > > > > > get exported to Excel. Yes - we only notced this after
> > SP1.
> >> > >> > > > > >
> >> > >> > > > > > It is obvious that this is a bug (a pretty big one at
> > that).
> >> I
> >> > >> > don't want
> >> > >> > > > > > to get into a "p*ss*ng contest" about this but am tired
of
> >> the
> >> > > back
> >> > >> > and
> >> > >> > > > > > forth
> >> > >> > > > > > about submitting a report case. It is simply a bug that
> >> > >> > > > > > is
> >> > >> > relatively
> >> > >> > > > > > simple
> >> > >> > > > > > to reproduce.
> >> > >> > > > > >
> >> > >> > > > > >
> >> > >> > > > > > "Bruce L-C [MVP]" wrote:
> >> > >> > > > > >
> >> > >> > > > > >> If you have universal you need to just post via a
managed
> >> > > newsgroup
> >> > >> > (if
> >> > >> > > > > >> you
> >> > >> > > > > >> haven't done this you post with a special fake email
> > address
> >> > > that
> >> > >> > you
> >> > >> > > > > >> have
> >> > >> > > > > >> registered in MSDN website and then someone from MS
will
> >> > >> > > > > >> answer
> >> > > and
> >> > >> > take
> >> > >> > > > > >> your repro case.
> >> > >> > > > > >>
> >> > >> > > > > >> I still think you have a misconception about this
> > newsgroup,
> >> > > that
> >> > >> > someone
> >> > >> > > > > >> from MS is watching every thread and that there should
be
> >> some
> >> > > sort
> >> > >> > of
> >> > >> > > > > >> official statement from them. That is not how it works.
> >> > >> > > > > >> If
> >> > > Brian
> >> > >> > happens
> >> > >> > > > > >> to
> >> > >> > > > > >> stop by then he might do something with it. I noticed
> >> > >> > > > > >> that
> >> he
> >> > > first
> >> > >> > said
> >> > >> > > > > >> the
> >> > >> > > > > >> best thing was to get product support involved and then
> >> > >> > > > > >> he
> >> > > mentions
> >> > >> > > > > >> posting.
> >> > >> > > > > >> So he went both ways with his answer. Posting might get
a
> >> > > response,
> >> > >> > with
> >> > >> > > > > >> managed newsgroup or product support you will get a
> >> response.
> >> > >> > Otherwise
> >> > >> > > > > >> it
> >> > >> > > > > >> is peer.
> >> > >> > > > > >> --
> >> > >> > > > > >> Bruce Loehle-Conger
> >> > >> > > > > >> MVP SQL Server Reporting Services
> >> > >> > > > > >>
> >> > >> > > > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
wrote
> > in
> >> > > message
> >> > >> > > > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> >> > >> > > > > >> > Read the whole thread, Brian Welcker said "you can
> >> > >> > > > > >> > post
> >> it
> >> > > here
> >> > >> > but
> >> > >> > > > > >> > for
> >> > >> > > > > >> us
> >> > >> > > > > >> > to repro, we would need more than a general problem
> >> > > statement"
> >> > >> > etc.
> >> > >> > > > > >> > This
> >> > >> > > > > >> is
> >> > >> > > > > >> > exactly what I did way back (I found my old file and
> >> posted
> >> > > it
> >> > >> > again).
> >> > >> > > > > >> > The
> >> > >> > > > > >> > same issue crops up, actually frequently, and an MS
> >> employee
> >> > > does
> >> > >> > not
> >> > >> > > > > >> > say
> >> > >> > > > > >> > it's a bug, don't they know yet, or do they only tell
> >> people
> >> > > that
> >> > >> > > > > >> > contact
> >> > >> > > > > >> > the product support team?
> >> > >> > > > > >> >
> >> > >> > > > > >> > Our company has a universal MSDN subscription, and I
am
> >> not
> >> > >> > hunting
> >> > >> > > > > >> > this
> >> > >> > > > > >> > issue, I bumped into the thread by accident, but
could
> > not
> >> > > keep
> >> > >> > quiet -
> >> > >> > > > > >> > something walks and quacks like a duck.
> >> > >> > > > > >> >
> >> > >> > > > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote
in
> >> > > message
> >> > >> > > > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> >> > >> > > > > >> > > I just changed my view to see all messages and I
then
> >> see
> >> > > that
> >> > >> > this
> >> > >> > > > > >> > > is a
> >> > >> > > > > >> > > continuation of a posting from awhile back.
> >> > >> > > > > >> > >
> >> > >> > > > > >> > > It sounds like
> >> > >> > > > > >> > > 1. you have a work around.
> >> > >> > > > > >> > > 2. you want support from this newsgroup for your
> > problem
> >> > >> > > > > >> > > 3. you don't want to submit a support incident
> >> > >> > > > > >> > >
> >> > >> > > > > >> > > So, however much you feel like #2 should be
happening
> >> for
> >> > > you,
> >> > >> > that
> >> > >> > > > > >> isn't
> >> > >> > > > > >> > > how the newsgroup is setup to operate. You either
> >> > >> > > > > >> > > need
> >> to
> >> > > open
> >> > >> > an
> >> > >> > > > > >> incident
> >> > >> > > > > >> > > or have an msdn subscription. The only people that
> >> > >> > > > > >> > > get
> >> any
> >> > >> > support
> >> > >> > > > > >> > > other
> >> > >> > > > > >> > > than peer support is if you are an MSDN
subscription
> >> > >> > > > > >> > > holder
> >> > > in
> >> > >> > which
> >> > >> > > > > >> case
> >> > >> > > > > >> > > you this newsgroup is part of the managed
newsgroups.
> >> > >> > > > > >> > >
> >> > >> > > > > >> > >
> >> > >> > > > > >> > > --
> >> > >> > > > > >> > > Bruce Loehle-Conger
> >> > >> > > > > >> > > MVP SQL Server Reporting Services
> >> > >> > > > > >> > >
> >> > >> > > > > >> > >
> >> > >> > > > > >> > >
> >> > >> > > > > >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> > wrote
> >> > >> > > > > >> > > in
> >> > >> > message
> >> > >> > > > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> >> > >> > > > > >> > > > If opening a support case would have fixed the
> > problem
> >> > > this
> >> > >> > month,
> >> > >> > > > > >> then
> >> > >> > > > > >> > it
> >> > >> > > > > >> > > > might have been worth the effort.
> >> > >> > > > > >> > > > I posted this problem just after the release of
SP1
> >> > > (without
> >> > >> > SP1
> >> > >> > > > > >> > > > one
> >> > >> > > > > >> > > cannot
> >> > >> > > > > >> > > > export to Excel 2000), many others posted it
since
> >> then,
> >> > > and
> >> > >> > even
> >> > >> > > > > >> > > > if I
> >> > >> > > > > >> > > filed
> >> > >> > > > > >> > > > an incident then, there is no such thing as SP2
> >> > >> > > > > >> > > > yet,
> >> and
> >> > > the
> >> > >> > client
> >> > >> > > > > >> > would
> >> > >> > > > > >> > > > have been off the roof by now.
> >> > >> > > > > >> > > > What I don't understand is why the MS guys don't
> > just
> >> > > admit
> >> > >> > that it
> >> > >> > > > > >> > > > is
> >> > >> > > > > >> a
> >> > >> > > > > >> > > > problem and suggest a work-around or release a
> > hot-fix
> >> > >> > > > > >> > > > or
> >> > >> > > > > >> > > > something.
> >> > >> > > > > >> As
> >> > >> > > > > >> > I
> >> > >> > > > > >> > > > said, I found sizing the stuff above the table
like
> >> > > headers,
> >> > >> > other
> >> > >> > > > > >> text,
> >> > >> > > > > >> > > > etc, fixes the problem (haven't had any
complaints
> >> from
> >> > > the
> >> > >> > > > > >> > > > client),
> >> > >> > > > > >> and
> >> > >> > > > > >> > > the
> >> > >> > > > > >> > > > report that looses the last row, attached to my
> > other
> >> > >> > posting, was
> >> > >> > > > > >> fixed
> >> > >> > > > > >> > > > like this and is running at the client.
> >> > >> > > > > >> > > >
> >> > >> > > > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com>
> >> > >> > > > > >> > > > wrote
> >> in
> >> > >> > message
> >> > >> > > > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> >> > >> > > > > >> > > > > I suggest opening up a support case. If it is a
> > bug
> >> > >> > > > > >> > > > > you
> >> > >> > don't get
> >> > >> > > > > >> > > charged.
> >> > >> > > > > >> > > > >
> >> > >> > > > > >> > > > > --
> >> > >> > > > > >> > > > > Bruce Loehle-Conger
> >> > >> > > > > >> > > > > MVP SQL Server Reporting Services
> >> > >> > > > > >> > > > >
> >> > >> > > > > >> > > > > "Chris Botha"
> >> > >> > > > > >> > > > > <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> >> > > wrote in
> >> > >> > > > > >> > > > > message
> >> > >> > > > > >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> >> > >> > > > > >> > > > > > Hopefully by now you found a work-around, but
> >> > >> > > > > >> > > > > > in
> >> > >> > > > > >> > > > > > case
> >> > > you
> >> > >> > did
> >> > >> > > > > >> > > > > > not,
> >> > >> > > > > >> I
> >> > >> > > > > >> > > > found
> >> > >> > > > > >> > > > > > that if I re-arrange the stuff above the
table
> > a
> >> > > bit,
> >> > >> > like
> >> > >> > > > > >> headers
> >> > >> > > > > >> > > and
> >> > >> > > > > >> > > > > > other text, etc, it fixes the problem.
> >> > >> > > > > >> > > > > >
> >> > >> > > > > >> > > > > > "chanley54"
> > <chanley54@.discussions.microsoft.com>
> >> > > wrote
> >> > >> > in
> >> > >> > > > > >> > > > > > message
> >> > >> > > > > >> > > > > >
> >> > >> > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> >> > >> > > > > >> > > > > > > Hello,
> >> > >> > > > > >> > > > > > >
> >> > >> > > > > >> > > > > > > This question has been posted a few times
and
> > is
> >> > >> > DEFINITELY A
> >> > >> > > > > >> SHOW
> >> > >> > > > > >> > > > > STOPPER
> >> > >> > > > > >> > > > > > > for Reporting Services.
> >> > >> > > > > >> > > > > > >
> >> > >> > > > > >> > > > > > > When exporting to Excel - the last row can
> > turn
> >> up
> >> > >> > missing -
> >> > >> > > > > >> > > > > > > Why
> >> > >> > > > > >> > is
> >> > >> > > > > >> > > > > > > Microsoft not responding to this?
> >> > >> > > > > >> > > > > > >
> >> > >> > > > > >> > > > > >
> >> > >> > > > > >> > > > > >
> >> > >> > > > > >> > > > >
> >> > >> > > > > >> > > > >
> >> > >> > > > > >> > > >
> >> > >> > > > > >> > > >
> >> > >> > > > > >> > >
> >> > >> > > > > >> > >
> >> > >> > > > > >> >
> >> > >> > > > > >> >
> >> > >> > > > > >>
> >> > >> > > > > >>
> >> > >> > > > > >>
> >> > >> > > > >
> >> > >> > > > >
> >> > >> > > > >
> >> > >> >
> >> > >> >
> >> > >> >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
>|||Hi Bruce, thanks for the link. Unfortunately I could not find how to obtain
a "managed newsgroup registered alias" on the page. It's more on how to
configure Outlook Express, etc. Thanks again.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%23rFCOxuCFHA.3936@.TK2MSFTNGP09.phx.gbl...
> This explains all about it.
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
> news:e%23z9okuCFHA.4004@.tk2msftngp13.phx.gbl...
>> They obviously "don't want to" touch this one. Can you tell me what the
>> steps are to get a "managed newsgroup registered alias", or point me to a
>> page where the information is? We are a MSDN Universal subscriber. I will
>> then start a thread for this issue and see if I can lure them in. Thanks.
>>
>> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
>> news:O$buPUuCFHA.3504@.TK2MSFTNGP12.phx.gbl...
>> > This is a peer supported newsgroups unless you post (not add in a
> response
>> > but start a post) using your managed newsgroup registered alias. If you
> do
>> > that (and you have MSDN so you should be able to do this) then they
>> > will
>> > answer you. Otherwise any MS posts are mostly people that jump on from
>> > time
>> > to time but it is not their job to answer questions. They do this
> because
>> > they want to.
>> >
>> > If you have a support call that turns out to be a bug you are not
> charged.
>> > I
>> > find it easier to use my managed newsgroup alias (I have two different
>> > connections to this newsgroup) when I need an answer.
>> >
>> > --
>> > Bruce Loehle-Conger
>> > MVP SQL Server Reporting Services
>> >
>> > "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
>> > news:%23GbmxMuCFHA.464@.TK2MSFTNGP15.phx.gbl...
>> >> Brilliant! We obediently follow the procedures to get our posts
> noticed
>> > by
>> >> MS and... silence...
>> >>
>> >> Perhaps I should open a bug using our MSDN subscription instead...
>> >>
>> >> Thanks for the update and the ref to the bug list.
>> >>
>> >> "Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
>> >> news:ONAxfOnCFHA.392@.TK2MSFTNGP14.phx.gbl...
>> >> > Ever heard the story "The Emperor's new clothes", where the tailor
>> >> > said
>> >> > that anybody that could not see the emperor's new clothes did not
> have
>> >> good
>> >> > taste, or something like that, while the emperor was actually naked?
>> > This
>> >> > issue reminds me of it. When I bumped into it for the 1st time just
>> > after
>> >> > SP1, one then eager MS guy said he would look into it, but must have
>> > been
>> >> > side tracked, or was told that there is no such bug, and since then,
>> > every
>> >> > so often, some desperate soul will post this issue, and then the MS
>> >> > guys
>> >> > won't touch it. It is like say nothing, then there is nothing. I was
>> >> > thinking that maybe it was the Chief of Reporting Services or
>> >> > someone
>> > who
>> >> > knows someone important, close to Bill maybe, programmed this part,
> and
>> >> that
>> >> > they are not allowed to tell.
>> >> >
>> >> > Just look down the newsgroup to a post on 1/29/2005 8:55 AM (5 days
>> >> > ago)
>> >> by
>> >> > "chanley54", titled "For MS Development Team - SP2", where he asked
> if
>> > the
>> >> > issue is fixed in SP2, silence from the MS camp.
>> >> > The following link points to a list of bugs that are fixed by SP2
> Beta,
>> >> > dated 16 Dec 2004, and this issue is not mentioned there, however
> they
>> >> > mention that "the list may be updated".
>> >> > http://support.microsoft.com/default.aspx?scid=kb;en-us;889640
>> >> >
>> >> >
>> >> > "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
>> >> > news:OlA62DmCFHA.1432@.tk2msftngp13.phx.gbl...
>> >> > > Last post was 12/7/2004... Any news from MS on this one - I just
>> > bumped
>> >> > > into the same wall with Excel 2003 and SP1...
>> >> > >
>> >> > > Cheers!
>> >> > >
>> >> > > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
>> >> > > news:26BF4F85-ED31-4DE7-9468-441B07976F2E@.microsoft.com...
>> >> > >> Absolutely - I've got users breathing down my neck on this one.
>> >> > >>
>> >> > >> -- Chris
>> >> > >>
>> >> > >> "Chris Botha" wrote:
>> >> > >>
>> >> > >> > If this thing takes off on some other group or if you manage to
>> >> > >> > get
>> > a
>> >> > >> > response from the MS guys, do you mind sending me an email?
>> >> > >> > Thanks,
>> >> > >> >
>> >> > >> > Chris.
>> >> > >> >
>> >> > >> > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
>> >> > >> > news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
>> >> > >> > > Bruce,
>> >> > >> > >
>> >> > >> > > Correction - I changed my alias and searched through the
> Managed
>> >> > > NewsGroup
>> >> > >> > > section and it brought me to the following:
>> >> > >> > >
>> >> > >> > >
>> >> > >> >
>> >> > >
>> >>
>> >
> http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
>> >> > >> > >
>> >> > >> > > Again - MS says that we will have a response in two day.
> Sorry
>> > to
>> >> > > beat
>> >> > >> > this
>> >> > >> > > to death.
>> >> > >> > >
>> >> > >> > > "chanley54" wrote:
>> >> > >> > >
>> >> > >> > > > Bruce,
>> >> > >> > > >
>> >> > >> > > > That's exactly what I have been doing. We do appricate the
>> > help.
>> >> > > This
>> >> > >> > > > posting was made through the same process that you
> described.
>> >> > >> > > >
>> >> > >> > > > Perhaps I am doing something wrong but my return address
> shows
>> >> the
>> >> > >> > following:
>> >> > >> > > > "chanley54@.discussions.microsoft.com"
>> >> > >> > > >
>> >> > >> > > > Regards.
>> >> > >> > > >
>> >> > >> > > >
>> >> > >> > > > "Bruce L-C [MVP]" wrote:
>> >> > >> > > >
>> >> > >> > > > > I am trying to help you. Remember before attacking me
>> >> > >> > > > > that
> I
>> >> help
>> >> > >> > people
>> >> > >> > > > > just for the hell of it. As such I am trying to let you
> know
>> >> how
>> >> > >> > things work
>> >> > >> > > > > so you can successfully get your issue resolved.
>> >> > >> > > > >
>> >> > >> > > > > About managed newsgroups. There is no difference between
>> >> > >> > > > > this
>> >> > >> > newsgroup and
>> >> > >> > > > > a managed newsgroup. They are the same thing (whether you
>> >> > >> > > > > use
>> > a
>> >> > > web
>> >> > >> > > > > interface or a outlook express). To have your posting to
> be
>> >> > > included
>> >> > >> > under
>> >> > >> > > > > the managed newsgroup support terms (I believe it is
> within
>> >> > >> > > > > 2
>> >> > > business
>> >> > >> > days)
>> >> > >> > > > > you have to do two things.
>> >> > >> > > > > - you have to initiate the posting. The software they use
> to
>> >> > > manage
>> >> > >> > the
>> >> > >> > > > > process only looks at whoever started the thread.
>> >> > >> > > > > - the return email address has to be the fake one
> registered
>> > as
>> >> > > part
>> >> > >> > of the
>> >> > >> > > > > managed newsgroup process. I'm not positive but looking
>> >> > >> > > > > at
>> > your
>> >> > > email
>> >> > >> > > > > address for your post it does not look to me like it is
> the
>> >> fake
>> >> > > one
>> >> > >> > > > > registered with MS. If they do not see the one that has
> been
>> >> > >> > registered with
>> >> > >> > > > > them then it is ignored. Note that this is not the email
>> >> address
>> >> > > that
>> >> > >> > the
>> >> > >> > > > > MSDN subscription has for you (i.e. it is NOT the
>> >> > >> > > > > passport
>> >> email
>> >> > >> > address,
>> >> > >> > > > > you have to specifically register an additional fake one
>> >> > >> > > > > that
>> >> is
>> >> > >> > > > > specifically for the managed newsgroup support).
>> >> > >> > > > >
>> >> > >> > > > > Go here:
>> >> > >> > > > > http://msdn.microsoft.com/newsgroups/managed/
>> >> > >> > > > >
>> >> > >> > > > > Login with passport
>> >> > >> > > > >
>> >> > >> > > > > Then scroll down to here:
>> >> > >> > > > > Getting Started
>> >> > >> > > > > The managed newsgroups are easy to use. Just follow these
>> >> simple
>> >> > >> > > > > instructions:
>> >> > >> > > > >
>> >> > >> > > > > a.. Register by creating your unique no-spam alias
>> >> > >> > > > > And click on the link.
>> >> > >> > > > >
>> >> > >> > > > > I didn't find it real intuitive about how it operates
> (first
>> >> > > posting,
>> >> > >> > using
>> >> > >> > > > > the alias)
>> >> > >> > > > >
>> >> > >> > > > >
>> >> > >> > > > > --
>> >> > >> > > > > Bruce Loehle-Conger
>> >> > >> > > > > MVP SQL Server Reporting Services
>> >> > >> > > > >
>> >> > >> > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote
>> >> > >> > > > > in
>> >> > >> > > > > message
>> >> > >> > > > > news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
>> >> > >> > > > > >I am posting this through the "Managed NewsGroup"
>> >> > >> > > > > >
>> >> > >> >
>> >> > >
>> >>
>> >
> http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
>> >> > >> > > > > >
>> >> > >> > > > > > and am still not getting an answer. I also have an
>> >> > >> > > > > > MSDN
>> >> > >> > subscription.
>> >> > >> > > > > > Based upon the above postings - shouldn't I get a
> response
>> >> > >> > > > > > back?
>> >> > >> > > > > >
>> >> > >> > > > > > The workaround will not work for me as we have almost a
>> > 1,000
>> >> > >> > reports that
>> >> > >> > > > > > get exported to Excel. Yes - we only notced this after
>> > SP1.
>> >> > >> > > > > >
>> >> > >> > > > > > It is obvious that this is a bug (a pretty big one at
>> > that).
>> >> I
>> >> > >> > don't want
>> >> > >> > > > > > to get into a "p*ss*ng contest" about this but am tired
> of
>> >> the
>> >> > > back
>> >> > >> > and
>> >> > >> > > > > > forth
>> >> > >> > > > > > about submitting a report case. It is simply a bug
>> >> > >> > > > > > that
>> >> > >> > > > > > is
>> >> > >> > relatively
>> >> > >> > > > > > simple
>> >> > >> > > > > > to reproduce.
>> >> > >> > > > > >
>> >> > >> > > > > >
>> >> > >> > > > > > "Bruce L-C [MVP]" wrote:
>> >> > >> > > > > >
>> >> > >> > > > > >> If you have universal you need to just post via a
> managed
>> >> > > newsgroup
>> >> > >> > (if
>> >> > >> > > > > >> you
>> >> > >> > > > > >> haven't done this you post with a special fake email
>> > address
>> >> > > that
>> >> > >> > you
>> >> > >> > > > > >> have
>> >> > >> > > > > >> registered in MSDN website and then someone from MS
> will
>> >> > >> > > > > >> answer
>> >> > > and
>> >> > >> > take
>> >> > >> > > > > >> your repro case.
>> >> > >> > > > > >>
>> >> > >> > > > > >> I still think you have a misconception about this
>> > newsgroup,
>> >> > > that
>> >> > >> > someone
>> >> > >> > > > > >> from MS is watching every thread and that there should
> be
>> >> some
>> >> > > sort
>> >> > >> > of
>> >> > >> > > > > >> official statement from them. That is not how it
>> >> > >> > > > > >> works.
>> >> > >> > > > > >> If
>> >> > > Brian
>> >> > >> > happens
>> >> > >> > > > > >> to
>> >> > >> > > > > >> stop by then he might do something with it. I noticed
>> >> > >> > > > > >> that
>> >> he
>> >> > > first
>> >> > >> > said
>> >> > >> > > > > >> the
>> >> > >> > > > > >> best thing was to get product support involved and
>> >> > >> > > > > >> then
>> >> > >> > > > > >> he
>> >> > > mentions
>> >> > >> > > > > >> posting.
>> >> > >> > > > > >> So he went both ways with his answer. Posting might
>> >> > >> > > > > >> get
> a
>> >> > > response,
>> >> > >> > with
>> >> > >> > > > > >> managed newsgroup or product support you will get a
>> >> response.
>> >> > >> > Otherwise
>> >> > >> > > > > >> it
>> >> > >> > > > > >> is peer.
>> >> > >> > > > > >> --
>> >> > >> > > > > >> Bruce Loehle-Conger
>> >> > >> > > > > >> MVP SQL Server Reporting Services
>> >> > >> > > > > >>
>> >> > >> > > > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> wrote
>> > in
>> >> > > message
>> >> > >> > > > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
>> >> > >> > > > > >> > Read the whole thread, Brian Welcker said "you can
>> >> > >> > > > > >> > post
>> >> it
>> >> > > here
>> >> > >> > but
>> >> > >> > > > > >> > for
>> >> > >> > > > > >> us
>> >> > >> > > > > >> > to repro, we would need more than a general problem
>> >> > > statement"
>> >> > >> > etc.
>> >> > >> > > > > >> > This
>> >> > >> > > > > >> is
>> >> > >> > > > > >> > exactly what I did way back (I found my old file and
>> >> posted
>> >> > > it
>> >> > >> > again).
>> >> > >> > > > > >> > The
>> >> > >> > > > > >> > same issue crops up, actually frequently, and an MS
>> >> employee
>> >> > > does
>> >> > >> > not
>> >> > >> > > > > >> > say
>> >> > >> > > > > >> > it's a bug, don't they know yet, or do they only
>> >> > >> > > > > >> > tell
>> >> people
>> >> > > that
>> >> > >> > > > > >> > contact
>> >> > >> > > > > >> > the product support team?
>> >> > >> > > > > >> >
>> >> > >> > > > > >> > Our company has a universal MSDN subscription, and I
> am
>> >> not
>> >> > >> > hunting
>> >> > >> > > > > >> > this
>> >> > >> > > > > >> > issue, I bumped into the thread by accident, but
> could
>> > not
>> >> > > keep
>> >> > >> > quiet -
>> >> > >> > > > > >> > something walks and quacks like a duck.
>> >> > >> > > > > >> >
>> >> > >> > > > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote
> in
>> >> > > message
>> >> > >> > > > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
>> >> > >> > > > > >> > > I just changed my view to see all messages and I
> then
>> >> see
>> >> > > that
>> >> > >> > this
>> >> > >> > > > > >> > > is a
>> >> > >> > > > > >> > > continuation of a posting from awhile back.
>> >> > >> > > > > >> > >
>> >> > >> > > > > >> > > It sounds like
>> >> > >> > > > > >> > > 1. you have a work around.
>> >> > >> > > > > >> > > 2. you want support from this newsgroup for your
>> > problem
>> >> > >> > > > > >> > > 3. you don't want to submit a support incident
>> >> > >> > > > > >> > >
>> >> > >> > > > > >> > > So, however much you feel like #2 should be
> happening
>> >> for
>> >> > > you,
>> >> > >> > that
>> >> > >> > > > > >> isn't
>> >> > >> > > > > >> > > how the newsgroup is setup to operate. You either
>> >> > >> > > > > >> > > need
>> >> to
>> >> > > open
>> >> > >> > an
>> >> > >> > > > > >> incident
>> >> > >> > > > > >> > > or have an msdn subscription. The only people that
>> >> > >> > > > > >> > > get
>> >> any
>> >> > >> > support
>> >> > >> > > > > >> > > other
>> >> > >> > > > > >> > > than peer support is if you are an MSDN
> subscription
>> >> > >> > > > > >> > > holder
>> >> > > in
>> >> > >> > which
>> >> > >> > > > > >> case
>> >> > >> > > > > >> > > you this newsgroup is part of the managed
> newsgroups.
>> >> > >> > > > > >> > >
>> >> > >> > > > > >> > >
>> >> > >> > > > > >> > > --
>> >> > >> > > > > >> > > Bruce Loehle-Conger
>> >> > >> > > > > >> > > MVP SQL Server Reporting Services
>> >> > >> > > > > >> > >
>> >> > >> > > > > >> > >
>> >> > >> > > > > >> > >
>> >> > >> > > > > >> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
>> > wrote
>> >> > >> > > > > >> > > in
>> >> > >> > message
>> >> > >> > > > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
>> >> > >> > > > > >> > > > If opening a support case would have fixed the
>> > problem
>> >> > > this
>> >> > >> > month,
>> >> > >> > > > > >> then
>> >> > >> > > > > >> > it
>> >> > >> > > > > >> > > > might have been worth the effort.
>> >> > >> > > > > >> > > > I posted this problem just after the release of
> SP1
>> >> > > (without
>> >> > >> > SP1
>> >> > >> > > > > >> > > > one
>> >> > >> > > > > >> > > cannot
>> >> > >> > > > > >> > > > export to Excel 2000), many others posted it
> since
>> >> then,
>> >> > > and
>> >> > >> > even
>> >> > >> > > > > >> > > > if I
>> >> > >> > > > > >> > > filed
>> >> > >> > > > > >> > > > an incident then, there is no such thing as SP2
>> >> > >> > > > > >> > > > yet,
>> >> and
>> >> > > the
>> >> > >> > client
>> >> > >> > > > > >> > would
>> >> > >> > > > > >> > > > have been off the roof by now.
>> >> > >> > > > > >> > > > What I don't understand is why the MS guys don't
>> > just
>> >> > > admit
>> >> > >> > that it
>> >> > >> > > > > >> > > > is
>> >> > >> > > > > >> a
>> >> > >> > > > > >> > > > problem and suggest a work-around or release a
>> > hot-fix
>> >> > >> > > > > >> > > > or
>> >> > >> > > > > >> > > > something.
>> >> > >> > > > > >> As
>> >> > >> > > > > >> > I
>> >> > >> > > > > >> > > > said, I found sizing the stuff above the table
> like
>> >> > > headers,
>> >> > >> > other
>> >> > >> > > > > >> text,
>> >> > >> > > > > >> > > > etc, fixes the problem (haven't had any
> complaints
>> >> from
>> >> > > the
>> >> > >> > > > > >> > > > client),
>> >> > >> > > > > >> and
>> >> > >> > > > > >> > > the
>> >> > >> > > > > >> > > > report that looses the last row, attached to my
>> > other
>> >> > >> > posting, was
>> >> > >> > > > > >> fixed
>> >> > >> > > > > >> > > > like this and is running at the client.
>> >> > >> > > > > >> > > >
>> >> > >> > > > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com>
>> >> > >> > > > > >> > > > wrote
>> >> in
>> >> > >> > message
>> >> > >> > > > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
>> >> > >> > > > > >> > > > > I suggest opening up a support case. If it is
>> >> > >> > > > > >> > > > > a
>> > bug
>> >> > >> > > > > >> > > > > you
>> >> > >> > don't get
>> >> > >> > > > > >> > > charged.
>> >> > >> > > > > >> > > > >
>> >> > >> > > > > >> > > > > --
>> >> > >> > > > > >> > > > > Bruce Loehle-Conger
>> >> > >> > > > > >> > > > > MVP SQL Server Reporting Services
>> >> > >> > > > > >> > > > >
>> >> > >> > > > > >> > > > > "Chris Botha"
>> >> > >> > > > > >> > > > > <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
>> >> > > wrote in
>> >> > >> > > > > >> > > > > message
>> >> > >> > > > > >> > > > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
>> >> > >> > > > > >> > > > > > Hopefully by now you found a work-around,
>> >> > >> > > > > >> > > > > > but
>> >> > >> > > > > >> > > > > > in
>> >> > >> > > > > >> > > > > > case
>> >> > > you
>> >> > >> > did
>> >> > >> > > > > >> > > > > > not,
>> >> > >> > > > > >> I
>> >> > >> > > > > >> > > > found
>> >> > >> > > > > >> > > > > > that if I re-arrange the stuff above the
> table
>> > a
>> >> > > bit,
>> >> > >> > like
>> >> > >> > > > > >> headers
>> >> > >> > > > > >> > > and
>> >> > >> > > > > >> > > > > > other text, etc, it fixes the problem.
>> >> > >> > > > > >> > > > > >
>> >> > >> > > > > >> > > > > > "chanley54"
>> > <chanley54@.discussions.microsoft.com>
>> >> > > wrote
>> >> > >> > in
>> >> > >> > > > > >> > > > > > message
>> >> > >> > > > > >> > > > > >
>> >> > >> > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
>> >> > >> > > > > >> > > > > > > Hello,
>> >> > >> > > > > >> > > > > > >
>> >> > >> > > > > >> > > > > > > This question has been posted a few times
> and
>> > is
>> >> > >> > DEFINITELY A
>> >> > >> > > > > >> SHOW
>> >> > >> > > > > >> > > > > STOPPER
>> >> > >> > > > > >> > > > > > > for Reporting Services.
>> >> > >> > > > > >> > > > > > >
>> >> > >> > > > > >> > > > > > > When exporting to Excel - the last row can
>> > turn
>> >> up
>> >> > >> > missing -
>> >> > >> > > > > >> > > > > > > Why
>> >> > >> > > > > >> > is
>> >> > >> > > > > >> > > > > > > Microsoft not responding to this?
>> >> > >> > > > > >> > > > > > >
>> >> > >> > > > > >> > > > > >
>> >> > >> > > > > >> > > > > >
>> >> > >> > > > > >> > > > >
>> >> > >> > > > > >> > > > >
>> >> > >> > > > > >> > > >
>> >> > >> > > > > >> > > >
>> >> > >> > > > > >> > >
>> >> > >> > > > > >> > >
>> >> > >> > > > > >> >
>> >> > >> > > > > >> >
>> >> > >> > > > > >>
>> >> > >> > > > > >>
>> >> > >> > > > > >>
>> >> > >> > > > >
>> >> > >> > > > >
>> >> > >> > > > >
>> >> > >> >
>> >> > >> >
>> >> > >> >
>> >> > >
>> >> > >
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>|||I followed the instructions in the _original_ link from Bruce as snipped
below:
<< From Bruce>>
About managed newsgroups. There is no difference between this newsgroup
and a managed newsgroup. They are the same thing (whether you use a web
interface or a outlook express). To have your posting to be included under
the managed newsgroup support terms (I believe it is within 2 business days)
you have to do two things.
- you have to initiate the posting. The software they use to manage the
process only looks at whoever started the thread.
- the return email address has to be the fake one registered as part of
the managed newsgroup process. If they do not see the one that has been
registered with them then it is ignored. Note that this is not the email
address that the MSDN subscription has for you (i.e. it is NOT the passport
email address, you have to specifically register an additional fake one that
is specifically for the managed newsgroup support).
Go here:
http://msdn.microsoft.com/newsgroups/managed/
Login with passport
Then scroll down to here:
Getting Started
The managed newsgroups are easy to use. Just follow these simple
instructions:
a.. Register by creating your unique no-spam alias And click on the
link.
I didn't find it real intuitive about how it operates (first posting,
using the alias).
<<\ From Bruce>>
BTW, Bruce's comment about the lack of intuitiveness is VERY appropo...
Once your nospam alias has been accepted, the page from the link below about
configuring Outlook comes up. Follow the bouncing ball and you should be
able to post using the alias and thereby gain the attention of MS personnel
(whose persistence and patience with us IS acknowledged and appreciated).
"Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
news:OuwPZFvCFHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi Bruce, thanks for the link. Unfortunately I could not find how to
obtain
> a "managed newsgroup registered alias" on the page. It's more on how to
> configure Outlook Express, etc. Thanks again.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%23rFCOxuCFHA.3936@.TK2MSFTNGP09.phx.gbl...
> > This explains all about it.
> > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
> > news:e%23z9okuCFHA.4004@.tk2msftngp13.phx.gbl...
> >> They obviously "don't want to" touch this one. Can you tell me what the
> >> steps are to get a "managed newsgroup registered alias", or point me to
a
> >> page where the information is? We are a MSDN Universal subscriber. I
will
> >> then start a thread for this issue and see if I can lure them in.
Thanks.
> >>
> >>
> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> >> news:O$buPUuCFHA.3504@.TK2MSFTNGP12.phx.gbl...
> >> > This is a peer supported newsgroups unless you post (not add in a
> > response
> >> > but start a post) using your managed newsgroup registered alias. If
you
> > do
> >> > that (and you have MSDN so you should be able to do this) then they
> >> > will
> >> > answer you. Otherwise any MS posts are mostly people that jump on
from
> >> > time
> >> > to time but it is not their job to answer questions. They do this
> > because
> >> > they want to.
> >> >
> >> > If you have a support call that turns out to be a bug you are not
> > charged.
> >> > I
> >> > find it easier to use my managed newsgroup alias (I have two
different
> >> > connections to this newsgroup) when I need an answer.
> >> >
> >> > --
> >> > Bruce Loehle-Conger
> >> > MVP SQL Server Reporting Services
> >> >
> >> > "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
> >> > news:%23GbmxMuCFHA.464@.TK2MSFTNGP15.phx.gbl...
> >> >> Brilliant! We obediently follow the procedures to get our posts
> > noticed
> >> > by
> >> >> MS and... silence...
> >> >>
> >> >> Perhaps I should open a bug using our MSDN subscription instead...
> >> >>
> >> >> Thanks for the update and the ref to the bug list.
> >> >>
> >> >> "Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
> >> >> news:ONAxfOnCFHA.392@.TK2MSFTNGP14.phx.gbl...
> >> >> > Ever heard the story "The Emperor's new clothes", where the
tailor
> >> >> > said
> >> >> > that anybody that could not see the emperor's new clothes did not
> > have
> >> >> good
> >> >> > taste, or something like that, while the emperor was actually
naked?
> >> > This
> >> >> > issue reminds me of it. When I bumped into it for the 1st time
just
> >> > after
> >> >> > SP1, one then eager MS guy said he would look into it, but must
have
> >> > been
> >> >> > side tracked, or was told that there is no such bug, and since
then,
> >> > every
> >> >> > so often, some desperate soul will post this issue, and then the
MS
> >> >> > guys
> >> >> > won't touch it. It is like say nothing, then there is nothing. I
was
> >> >> > thinking that maybe it was the Chief of Reporting Services or
> >> >> > someone
> >> > who
> >> >> > knows someone important, close to Bill maybe, programmed this
part,
> > and
> >> >> that
> >> >> > they are not allowed to tell.
> >> >> >
> >> >> > Just look down the newsgroup to a post on 1/29/2005 8:55 AM (5
days
> >> >> > ago)
> >> >> by
> >> >> > "chanley54", titled "For MS Development Team - SP2", where he
asked
> > if
> >> > the
> >> >> > issue is fixed in SP2, silence from the MS camp.
> >> >> > The following link points to a list of bugs that are fixed by SP2
> > Beta,
> >> >> > dated 16 Dec 2004, and this issue is not mentioned there, however
> > they
> >> >> > mention that "the list may be updated".
> >> >> > http://support.microsoft.com/default.aspx?scid=kb;en-us;889640
> >> >> >
> >> >> >
> >> >> > "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
> >> >> > news:OlA62DmCFHA.1432@.tk2msftngp13.phx.gbl...
> >> >> > > Last post was 12/7/2004... Any news from MS on this one - I
just
> >> > bumped
> >> >> > > into the same wall with Excel 2003 and SP1...
> >> >> > >
> >> >> > > Cheers!
> >> >> > >
> >> >> > > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> >> >> > > news:26BF4F85-ED31-4DE7-9468-441B07976F2E@.microsoft.com...
> >> >> > >> Absolutely - I've got users breathing down my neck on this one.
> >> >> > >>
> >> >> > >> -- Chris
> >> >> > >>
> >> >> > >> "Chris Botha" wrote:
> >> >> > >>
> >> >> > >> > If this thing takes off on some other group or if you manage
to
> >> >> > >> > get
> >> > a
> >> >> > >> > response from the MS guys, do you mind sending me an email?
> >> >> > >> > Thanks,
> >> >> > >> >
> >> >> > >> > Chris.
> >> >> > >> >
> >> >> > >> > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> >> >> > >> > news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
> >> >> > >> > > Bruce,
> >> >> > >> > >
> >> >> > >> > > Correction - I changed my alias and searched through the
> > Managed
> >> >> > > NewsGroup
> >> >> > >> > > section and it brought me to the following:
> >> >> > >> > >
> >> >> > >> > >
> >> >> > >> >
> >> >> > >
> >> >>
> >> >
> >
http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&exp=&sloc=en-us
> >> >> > >> > >
> >> >> > >> > > Again - MS says that we will have a response in two day.
> > Sorry
> >> > to
> >> >> > > beat
> >> >> > >> > this
> >> >> > >> > > to death.
> >> >> > >> > >
> >> >> > >> > > "chanley54" wrote:
> >> >> > >> > >
> >> >> > >> > > > Bruce,
> >> >> > >> > > >
> >> >> > >> > > > That's exactly what I have been doing. We do appricate
the
> >> > help.
> >> >> > > This
> >> >> > >> > > > posting was made through the same process that you
> > described.
> >> >> > >> > > >
> >> >> > >> > > > Perhaps I am doing something wrong but my return address
> > shows
> >> >> the
> >> >> > >> > following:
> >> >> > >> > > > "chanley54@.discussions.microsoft.com"
> >> >> > >> > > >
> >> >> > >> > > > Regards.
> >> >> > >> > > >
> >> >> > >> > > >
> >> >> > >> > > > "Bruce L-C [MVP]" wrote:
> >> >> > >> > > >
> >> >> > >> > > > > I am trying to help you. Remember before attacking me
> >> >> > >> > > > > that
> > I
> >> >> help
> >> >> > >> > people
> >> >> > >> > > > > just for the hell of it. As such I am trying to let you
> > know
> >> >> how
> >> >> > >> > things work
> >> >> > >> > > > > so you can successfully get your issue resolved.
> >> >> > >> > > > >
> >> >> > >> > > > > About managed newsgroups. There is no difference
between
> >> >> > >> > > > > this
> >> >> > >> > newsgroup and
> >> >> > >> > > > > a managed newsgroup. They are the same thing (whether
you
> >> >> > >> > > > > use
> >> > a
> >> >> > > web
> >> >> > >> > > > > interface or a outlook express). To have your posting
to
> > be
> >> >> > > included
> >> >> > >> > under
> >> >> > >> > > > > the managed newsgroup support terms (I believe it is
> > within
> >> >> > >> > > > > 2
> >> >> > > business
> >> >> > >> > days)
> >> >> > >> > > > > you have to do two things.
> >> >> > >> > > > > - you have to initiate the posting. The software they
use
> > to
> >> >> > > manage
> >> >> > >> > the
> >> >> > >> > > > > process only looks at whoever started the thread.
> >> >> > >> > > > > - the return email address has to be the fake one
> > registered
> >> > as
> >> >> > > part
> >> >> > >> > of the
> >> >> > >> > > > > managed newsgroup process. I'm not positive but looking
> >> >> > >> > > > > at
> >> > your
> >> >> > > email
> >> >> > >> > > > > address for your post it does not look to me like it is
> > the
> >> >> fake
> >> >> > > one
> >> >> > >> > > > > registered with MS. If they do not see the one that has
> > been
> >> >> > >> > registered with
> >> >> > >> > > > > them then it is ignored. Note that this is not the
email
> >> >> address
> >> >> > > that
> >> >> > >> > the
> >> >> > >> > > > > MSDN subscription has for you (i.e. it is NOT the
> >> >> > >> > > > > passport
> >> >> email
> >> >> > >> > address,
> >> >> > >> > > > > you have to specifically register an additional fake
one
> >> >> > >> > > > > that
> >> >> is
> >> >> > >> > > > > specifically for the managed newsgroup support).
> >> >> > >> > > > >
> >> >> > >> > > > > Go here:
> >> >> > >> > > > > http://msdn.microsoft.com/newsgroups/managed/
> >> >> > >> > > > >
> >> >> > >> > > > > Login with passport
> >> >> > >> > > > >
> >> >> > >> > > > > Then scroll down to here:
> >> >> > >> > > > > Getting Started
> >> >> > >> > > > > The managed newsgroups are easy to use. Just follow
these
> >> >> simple
> >> >> > >> > > > > instructions:
> >> >> > >> > > > >
> >> >> > >> > > > > a.. Register by creating your unique no-spam alias
> >> >> > >> > > > > And click on the link.
> >> >> > >> > > > >
> >> >> > >> > > > > I didn't find it real intuitive about how it operates
> > (first
> >> >> > > posting,
> >> >> > >> > using
> >> >> > >> > > > > the alias)
> >> >> > >> > > > >
> >> >> > >> > > > >
> >> >> > >> > > > > --
> >> >> > >> > > > > Bruce Loehle-Conger
> >> >> > >> > > > > MVP SQL Server Reporting Services
> >> >> > >> > > > >
> >> >> > >> > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote
> >> >> > >> > > > > in
> >> >> > >> > > > > message
> >> >> > >> > > > >
news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
> >> >> > >> > > > > >I am posting this through the "Managed NewsGroup"
> >> >> > >> > > > > >
> >> >> > >> >
> >> >> > >
> >> >>
> >> >
> >
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> >> >> > >> > > > > >
> >> >> > >> > > > > > and am still not getting an answer. I also have an
> >> >> > >> > > > > > MSDN
> >> >> > >> > subscription.
> >> >> > >> > > > > > Based upon the above postings - shouldn't I get a
> > response
> >> >> > >> > > > > > back?
> >> >> > >> > > > > >
> >> >> > >> > > > > > The workaround will not work for me as we have almost
a
> >> > 1,000
> >> >> > >> > reports that
> >> >> > >> > > > > > get exported to Excel. Yes - we only notced this
after
> >> > SP1.
> >> >> > >> > > > > >
> >> >> > >> > > > > > It is obvious that this is a bug (a pretty big one at
> >> > that).
> >> >> I
> >> >> > >> > don't want
> >> >> > >> > > > > > to get into a "p*ss*ng contest" about this but am
tired
> > of
> >> >> the
> >> >> > > back
> >> >> > >> > and
> >> >> > >> > > > > > forth
> >> >> > >> > > > > > about submitting a report case. It is simply a bug
> >> >> > >> > > > > > that
> >> >> > >> > > > > > is
> >> >> > >> > relatively
> >> >> > >> > > > > > simple
> >> >> > >> > > > > > to reproduce.
> >> >> > >> > > > > >
> >> >> > >> > > > > >
> >> >> > >> > > > > > "Bruce L-C [MVP]" wrote:
> >> >> > >> > > > > >
> >> >> > >> > > > > >> If you have universal you need to just post via a
> > managed
> >> >> > > newsgroup
> >> >> > >> > (if
> >> >> > >> > > > > >> you
> >> >> > >> > > > > >> haven't done this you post with a special fake email
> >> > address
> >> >> > > that
> >> >> > >> > you
> >> >> > >> > > > > >> have
> >> >> > >> > > > > >> registered in MSDN website and then someone from MS
> > will
> >> >> > >> > > > > >> answer
> >> >> > > and
> >> >> > >> > take
> >> >> > >> > > > > >> your repro case.
> >> >> > >> > > > > >>
> >> >> > >> > > > > >> I still think you have a misconception about this
> >> > newsgroup,
> >> >> > > that
> >> >> > >> > someone
> >> >> > >> > > > > >> from MS is watching every thread and that there
should
> > be
> >> >> some
> >> >> > > sort
> >> >> > >> > of
> >> >> > >> > > > > >> official statement from them. That is not how it
> >> >> > >> > > > > >> works.
> >> >> > >> > > > > >> If
> >> >> > > Brian
> >> >> > >> > happens
> >> >> > >> > > > > >> to
> >> >> > >> > > > > >> stop by then he might do something with it. I
noticed
> >> >> > >> > > > > >> that
> >> >> he
> >> >> > > first
> >> >> > >> > said
> >> >> > >> > > > > >> the
> >> >> > >> > > > > >> best thing was to get product support involved and
> >> >> > >> > > > > >> then
> >> >> > >> > > > > >> he
> >> >> > > mentions
> >> >> > >> > > > > >> posting.
> >> >> > >> > > > > >> So he went both ways with his answer. Posting might
> >> >> > >> > > > > >> get
> > a
> >> >> > > response,
> >> >> > >> > with
> >> >> > >> > > > > >> managed newsgroup or product support you will get a
> >> >> response.
> >> >> > >> > Otherwise
> >> >> > >> > > > > >> it
> >> >> > >> > > > > >> is peer.
> >> >> > >> > > > > >> --
> >> >> > >> > > > > >> Bruce Loehle-Conger
> >> >> > >> > > > > >> MVP SQL Server Reporting Services
> >> >> > >> > > > > >>
> >> >> > >> > > > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> > wrote
> >> > in
> >> >> > > message
> >> >> > >> > > > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> >> >> > >> > > > > >> > Read the whole thread, Brian Welcker said "you
can
> >> >> > >> > > > > >> > post
> >> >> it
> >> >> > > here
> >> >> > >> > but
> >> >> > >> > > > > >> > for
> >> >> > >> > > > > >> us
> >> >> > >> > > > > >> > to repro, we would need more than a general
problem
> >> >> > > statement"
> >> >> > >> > etc.
> >> >> > >> > > > > >> > This
> >> >> > >> > > > > >> is
> >> >> > >> > > > > >> > exactly what I did way back (I found my old file
and
> >> >> posted
> >> >> > > it
> >> >> > >> > again).
> >> >> > >> > > > > >> > The
> >> >> > >> > > > > >> > same issue crops up, actually frequently, and an
MS
> >> >> employee
> >> >> > > does
> >> >> > >> > not
> >> >> > >> > > > > >> > say
> >> >> > >> > > > > >> > it's a bug, don't they know yet, or do they only
> >> >> > >> > > > > >> > tell
> >> >> people
> >> >> > > that
> >> >> > >> > > > > >> > contact
> >> >> > >> > > > > >> > the product support team?
> >> >> > >> > > > > >> >
> >> >> > >> > > > > >> > Our company has a universal MSDN subscription, and
I
> > am
> >> >> not
> >> >> > >> > hunting
> >> >> > >> > > > > >> > this
> >> >> > >> > > > > >> > issue, I bumped into the thread by accident, but
> > could
> >> > not
> >> >> > > keep
> >> >> > >> > quiet -
> >> >> > >> > > > > >> > something walks and quacks like a duck.
> >> >> > >> > > > > >> >
> >> >> > >> > > > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com>
wrote
> > in
> >> >> > > message
> >> >> > >> > > > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> >> >> > >> > > > > >> > > I just changed my view to see all messages and I
> > then
> >> >> see
> >> >> > > that
> >> >> > >> > this
> >> >> > >> > > > > >> > > is a
> >> >> > >> > > > > >> > > continuation of a posting from awhile back.
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > > It sounds like
> >> >> > >> > > > > >> > > 1. you have a work around.
> >> >> > >> > > > > >> > > 2. you want support from this newsgroup for your
> >> > problem
> >> >> > >> > > > > >> > > 3. you don't want to submit a support incident
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > > So, however much you feel like #2 should be
> > happening
> >> >> for
> >> >> > > you,
> >> >> > >> > that
> >> >> > >> > > > > >> isn't
> >> >> > >> > > > > >> > > how the newsgroup is setup to operate. You
either
> >> >> > >> > > > > >> > > need
> >> >> to
> >> >> > > open
> >> >> > >> > an
> >> >> > >> > > > > >> incident
> >> >> > >> > > > > >> > > or have an msdn subscription. The only people
that
> >> >> > >> > > > > >> > > get
> >> >> any
> >> >> > >> > support
> >> >> > >> > > > > >> > > other
> >> >> > >> > > > > >> > > than peer support is if you are an MSDN
> > subscription
> >> >> > >> > > > > >> > > holder
> >> >> > > in
> >> >> > >> > which
> >> >> > >> > > > > >> case
> >> >> > >> > > > > >> > > you this newsgroup is part of the managed
> > newsgroups.
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > > --
> >> >> > >> > > > > >> > > Bruce Loehle-Conger
> >> >> > >> > > > > >> > > MVP SQL Server Reporting Services
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > > "Chris Botha"
<chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> >> > wrote
> >> >> > >> > > > > >> > > in
> >> >> > >> > message
> >> >> > >> > > > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> >> >> > >> > > > > >> > > > If opening a support case would have fixed the
> >> > problem
> >> >> > > this
> >> >> > >> > month,
> >> >> > >> > > > > >> then
> >> >> > >> > > > > >> > it
> >> >> > >> > > > > >> > > > might have been worth the effort.
> >> >> > >> > > > > >> > > > I posted this problem just after the release
of
> > SP1
> >> >> > > (without
> >> >> > >> > SP1
> >> >> > >> > > > > >> > > > one
> >> >> > >> > > > > >> > > cannot
> >> >> > >> > > > > >> > > > export to Excel 2000), many others posted it
> > since
> >> >> then,
> >> >> > > and
> >> >> > >> > even
> >> >> > >> > > > > >> > > > if I
> >> >> > >> > > > > >> > > filed
> >> >> > >> > > > > >> > > > an incident then, there is no such thing as
SP2
> >> >> > >> > > > > >> > > > yet,
> >> >> and
> >> >> > > the
> >> >> > >> > client
> >> >> > >> > > > > >> > would
> >> >> > >> > > > > >> > > > have been off the roof by now.
> >> >> > >> > > > > >> > > > What I don't understand is why the MS guys
don't
> >> > just
> >> >> > > admit
> >> >> > >> > that it
> >> >> > >> > > > > >> > > > is
> >> >> > >> > > > > >> a
> >> >> > >> > > > > >> > > > problem and suggest a work-around or release a
> >> > hot-fix
> >> >> > >> > > > > >> > > > or
> >> >> > >> > > > > >> > > > something.
> >> >> > >> > > > > >> As
> >> >> > >> > > > > >> > I
> >> >> > >> > > > > >> > > > said, I found sizing the stuff above the table
> > like
> >> >> > > headers,
> >> >> > >> > other
> >> >> > >> > > > > >> text,
> >> >> > >> > > > > >> > > > etc, fixes the problem (haven't had any
> > complaints
> >> >> from
> >> >> > > the
> >> >> > >> > > > > >> > > > client),
> >> >> > >> > > > > >> and
> >> >> > >> > > > > >> > > the
> >> >> > >> > > > > >> > > > report that looses the last row, attached to
my
> >> > other
> >> >> > >> > posting, was
> >> >> > >> > > > > >> fixed
> >> >> > >> > > > > >> > > > like this and is running at the client.
> >> >> > >> > > > > >> > > >
> >> >> > >> > > > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com>
> >> >> > >> > > > > >> > > > wrote
> >> >> in
> >> >> > >> > message
> >> >> > >> > > > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> >> >> > >> > > > > >> > > > > I suggest opening up a support case. If it
is
> >> >> > >> > > > > >> > > > > a
> >> > bug
> >> >> > >> > > > > >> > > > > you
> >> >> > >> > don't get
> >> >> > >> > > > > >> > > charged.
> >> >> > >> > > > > >> > > > >
> >> >> > >> > > > > >> > > > > --
> >> >> > >> > > > > >> > > > > Bruce Loehle-Conger
> >> >> > >> > > > > >> > > > > MVP SQL Server Reporting Services
> >> >> > >> > > > > >> > > > >
> >> >> > >> > > > > >> > > > > "Chris Botha"
> >> >> > >> > > > > >> > > > > <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> >> >> > > wrote in
> >> >> > >> > > > > >> > > > > message
> >> >> > >> > > > > >> > > > >
news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> >> >> > >> > > > > >> > > > > > Hopefully by now you found a work-around,
> >> >> > >> > > > > >> > > > > > but
> >> >> > >> > > > > >> > > > > > in
> >> >> > >> > > > > >> > > > > > case
> >> >> > > you
> >> >> > >> > did
> >> >> > >> > > > > >> > > > > > not,
> >> >> > >> > > > > >> I
> >> >> > >> > > > > >> > > > found
> >> >> > >> > > > > >> > > > > > that if I re-arrange the stuff above the
> > table
> >> > a
> >> >> > > bit,
> >> >> > >> > like
> >> >> > >> > > > > >> headers
> >> >> > >> > > > > >> > > and
> >> >> > >> > > > > >> > > > > > other text, etc, it fixes the problem.
> >> >> > >> > > > > >> > > > > >
> >> >> > >> > > > > >> > > > > > "chanley54"
> >> > <chanley54@.discussions.microsoft.com>
> >> >> > > wrote
> >> >> > >> > in
> >> >> > >> > > > > >> > > > > > message
> >> >> > >> > > > > >> > > > > >
> >> >> > >> > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> >> >> > >> > > > > >> > > > > > > Hello,
> >> >> > >> > > > > >> > > > > > >
> >> >> > >> > > > > >> > > > > > > This question has been posted a few
times
> > and
> >> > is
> >> >> > >> > DEFINITELY A
> >> >> > >> > > > > >> SHOW
> >> >> > >> > > > > >> > > > > STOPPER
> >> >> > >> > > > > >> > > > > > > for Reporting Services.
> >> >> > >> > > > > >> > > > > > >
> >> >> > >> > > > > >> > > > > > > When exporting to Excel - the last row
can
> >> > turn
> >> >> up
> >> >> > >> > missing -
> >> >> > >> > > > > >> > > > > > > Why
> >> >> > >> > > > > >> > is
> >> >> > >> > > > > >> > > > > > > Microsoft not responding to this?
> >> >> > >> > > > > >> > > > > > >
> >> >> > >> > > > > >> > > > > >
> >> >> > >> > > > > >> > > > > >
> >> >> > >> > > > > >> > > > >
> >> >> > >> > > > > >> > > > >
> >> >> > >> > > > > >> > > >
> >> >> > >> > > > > >> > > >
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> >
> >> >> > >> > > > > >> >
> >> >> > >> > > > > >>
> >> >> > >> > > > > >>
> >> >> > >> > > > > >>
> >> >> > >> > > > >
> >> >> > >> > > > >
> >> >> > >> > > > >
> >> >> > >> >
> >> >> > >> >
> >> >> > >> >
> >> >> > >
> >> >> > >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>|||That page has the link that you use to register your alias. Here is the key
phrase:
>>>>>
How do I register my email address to receive notifications of my posts?
If you have not created a profile you will need to do so at the web based
Managed Newsgroup site using your passport account.
>>>>>
I had trouble finding and registering this as well. They do not make it very
discoverable.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
news:OuwPZFvCFHA.1408@.TK2MSFTNGP10.phx.gbl...
> Hi Bruce, thanks for the link. Unfortunately I could not find how to
obtain
> a "managed newsgroup registered alias" on the page. It's more on how to
> configure Outlook Express, etc. Thanks again.
>
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:%23rFCOxuCFHA.3936@.TK2MSFTNGP09.phx.gbl...
> > This explains all about it.
> > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
> > news:e%23z9okuCFHA.4004@.tk2msftngp13.phx.gbl...
> >> They obviously "don't want to" touch this one. Can you tell me what the
> >> steps are to get a "managed newsgroup registered alias", or point me to
a
> >> page where the information is? We are a MSDN Universal subscriber. I
will
> >> then start a thread for this issue and see if I can lure them in.
Thanks.
> >>
> >>
> >> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> >> news:O$buPUuCFHA.3504@.TK2MSFTNGP12.phx.gbl...
> >> > This is a peer supported newsgroups unless you post (not add in a
> > response
> >> > but start a post) using your managed newsgroup registered alias. If
you
> > do
> >> > that (and you have MSDN so you should be able to do this) then they
> >> > will
> >> > answer you. Otherwise any MS posts are mostly people that jump on
from
> >> > time
> >> > to time but it is not their job to answer questions. They do this
> > because
> >> > they want to.
> >> >
> >> > If you have a support call that turns out to be a bug you are not
> > charged.
> >> > I
> >> > find it easier to use my managed newsgroup alias (I have two
different
> >> > connections to this newsgroup) when I need an answer.
> >> >
> >> > --
> >> > Bruce Loehle-Conger
> >> > MVP SQL Server Reporting Services
> >> >
> >> > "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
> >> > news:%23GbmxMuCFHA.464@.TK2MSFTNGP15.phx.gbl...
> >> >> Brilliant! We obediently follow the procedures to get our posts
> > noticed
> >> > by
> >> >> MS and... silence...
> >> >>
> >> >> Perhaps I should open a bug using our MSDN subscription instead...
> >> >>
> >> >> Thanks for the update and the ref to the bug list.
> >> >>
> >> >> "Chris Botha" <chris_s_botha@..AT.hotmail.com> wrote in message
> >> >> news:ONAxfOnCFHA.392@.TK2MSFTNGP14.phx.gbl...
> >> >> > Ever heard the story "The Emperor's new clothes", where the
tailor
> >> >> > said
> >> >> > that anybody that could not see the emperor's new clothes did not
> > have
> >> >> good
> >> >> > taste, or something like that, while the emperor was actually
naked?
> >> > This
> >> >> > issue reminds me of it. When I bumped into it for the 1st time
just
> >> > after
> >> >> > SP1, one then eager MS guy said he would look into it, but must
have
> >> > been
> >> >> > side tracked, or was told that there is no such bug, and since
then,
> >> > every
> >> >> > so often, some desperate soul will post this issue, and then the
MS
> >> >> > guys
> >> >> > won't touch it. It is like say nothing, then there is nothing. I
was
> >> >> > thinking that maybe it was the Chief of Reporting Services or
> >> >> > someone
> >> > who
> >> >> > knows someone important, close to Bill maybe, programmed this
part,
> > and
> >> >> that
> >> >> > they are not allowed to tell.
> >> >> >
> >> >> > Just look down the newsgroup to a post on 1/29/2005 8:55 AM (5
days
> >> >> > ago)
> >> >> by
> >> >> > "chanley54", titled "For MS Development Team - SP2", where he
asked
> > if
> >> > the
> >> >> > issue is fixed in SP2, silence from the MS camp.
> >> >> > The following link points to a list of bugs that are fixed by SP2
> > Beta,
> >> >> > dated 16 Dec 2004, and this issue is not mentioned there, however
> > they
> >> >> > mention that "the list may be updated".
> >> >> > http://support.microsoft.com/default.aspx?scid=kb;en-us;889640
> >> >> >
> >> >> >
> >> >> > "SS_Newbie" <SS_Newbie@.community.nospam> wrote in message
> >> >> > news:OlA62DmCFHA.1432@.tk2msftngp13.phx.gbl...
> >> >> > > Last post was 12/7/2004... Any news from MS on this one - I
just
> >> > bumped
> >> >> > > into the same wall with Excel 2003 and SP1...
> >> >> > >
> >> >> > > Cheers!
> >> >> > >
> >> >> > > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> >> >> > > news:26BF4F85-ED31-4DE7-9468-441B07976F2E@.microsoft.com...
> >> >> > >> Absolutely - I've got users breathing down my neck on this one.
> >> >> > >>
> >> >> > >> -- Chris
> >> >> > >>
> >> >> > >> "Chris Botha" wrote:
> >> >> > >>
> >> >> > >> > If this thing takes off on some other group or if you manage
to
> >> >> > >> > get
> >> > a
> >> >> > >> > response from the MS guys, do you mind sending me an email?
> >> >> > >> > Thanks,
> >> >> > >> >
> >> >> > >> > Chris.
> >> >> > >> >
> >> >> > >> > "chanley54" <chanley54@.newsgroup.nospam> wrote in message
> >> >> > >> > news:7466D2DA-EB4C-4324-BE0C-B85DBA72036A@.microsoft.com...
> >> >> > >> > > Bruce,
> >> >> > >> > >
> >> >> > >> > > Correction - I changed my alias and searched through the
> > Managed
> >> >> > > NewsGroup
> >> >> > >> > > section and it brought me to the following:
> >> >> > >> > >
> >> >> > >> > >
> >> >> > >> >
> >> >> > >
> >> >>
> >> >
> >
http://msdn.microsoft.com/newsgroups/managed/Default.aspx?query=Excel+Export+Missing&dg=&cat=en-us-msdnman&lang=en&cr=US&pt=&catlist=&dglist=&ptlist=&ex
p=&sloc=en-us
> >> >> > >> > >
> >> >> > >> > > Again - MS says that we will have a response in two day.
> > Sorry
> >> > to
> >> >> > > beat
> >> >> > >> > this
> >> >> > >> > > to death.
> >> >> > >> > >
> >> >> > >> > > "chanley54" wrote:
> >> >> > >> > >
> >> >> > >> > > > Bruce,
> >> >> > >> > > >
> >> >> > >> > > > That's exactly what I have been doing. We do appricate
the
> >> > help.
> >> >> > > This
> >> >> > >> > > > posting was made through the same process that you
> > described.
> >> >> > >> > > >
> >> >> > >> > > > Perhaps I am doing something wrong but my return address
> > shows
> >> >> the
> >> >> > >> > following:
> >> >> > >> > > > "chanley54@.discussions.microsoft.com"
> >> >> > >> > > >
> >> >> > >> > > > Regards.
> >> >> > >> > > >
> >> >> > >> > > >
> >> >> > >> > > > "Bruce L-C [MVP]" wrote:
> >> >> > >> > > >
> >> >> > >> > > > > I am trying to help you. Remember before attacking me
> >> >> > >> > > > > that
> > I
> >> >> help
> >> >> > >> > people
> >> >> > >> > > > > just for the hell of it. As such I am trying to let you
> > know
> >> >> how
> >> >> > >> > things work
> >> >> > >> > > > > so you can successfully get your issue resolved.
> >> >> > >> > > > >
> >> >> > >> > > > > About managed newsgroups. There is no difference
between
> >> >> > >> > > > > this
> >> >> > >> > newsgroup and
> >> >> > >> > > > > a managed newsgroup. They are the same thing (whether
you
> >> >> > >> > > > > use
> >> > a
> >> >> > > web
> >> >> > >> > > > > interface or a outlook express). To have your posting
to
> > be
> >> >> > > included
> >> >> > >> > under
> >> >> > >> > > > > the managed newsgroup support terms (I believe it is
> > within
> >> >> > >> > > > > 2
> >> >> > > business
> >> >> > >> > days)
> >> >> > >> > > > > you have to do two things.
> >> >> > >> > > > > - you have to initiate the posting. The software they
use
> > to
> >> >> > > manage
> >> >> > >> > the
> >> >> > >> > > > > process only looks at whoever started the thread.
> >> >> > >> > > > > - the return email address has to be the fake one
> > registered
> >> > as
> >> >> > > part
> >> >> > >> > of the
> >> >> > >> > > > > managed newsgroup process. I'm not positive but looking
> >> >> > >> > > > > at
> >> > your
> >> >> > > email
> >> >> > >> > > > > address for your post it does not look to me like it is
> > the
> >> >> fake
> >> >> > > one
> >> >> > >> > > > > registered with MS. If they do not see the one that has
> > been
> >> >> > >> > registered with
> >> >> > >> > > > > them then it is ignored. Note that this is not the
email
> >> >> address
> >> >> > > that
> >> >> > >> > the
> >> >> > >> > > > > MSDN subscription has for you (i.e. it is NOT the
> >> >> > >> > > > > passport
> >> >> email
> >> >> > >> > address,
> >> >> > >> > > > > you have to specifically register an additional fake
one
> >> >> > >> > > > > that
> >> >> is
> >> >> > >> > > > > specifically for the managed newsgroup support).
> >> >> > >> > > > >
> >> >> > >> > > > > Go here:
> >> >> > >> > > > > http://msdn.microsoft.com/newsgroups/managed/
> >> >> > >> > > > >
> >> >> > >> > > > > Login with passport
> >> >> > >> > > > >
> >> >> > >> > > > > Then scroll down to here:
> >> >> > >> > > > > Getting Started
> >> >> > >> > > > > The managed newsgroups are easy to use. Just follow
these
> >> >> simple
> >> >> > >> > > > > instructions:
> >> >> > >> > > > >
> >> >> > >> > > > > a.. Register by creating your unique no-spam alias
> >> >> > >> > > > > And click on the link.
> >> >> > >> > > > >
> >> >> > >> > > > > I didn't find it real intuitive about how it operates
> > (first
> >> >> > > posting,
> >> >> > >> > using
> >> >> > >> > > > > the alias)
> >> >> > >> > > > >
> >> >> > >> > > > >
> >> >> > >> > > > > --
> >> >> > >> > > > > Bruce Loehle-Conger
> >> >> > >> > > > > MVP SQL Server Reporting Services
> >> >> > >> > > > >
> >> >> > >> > > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote
> >> >> > >> > > > > in
> >> >> > >> > > > > message
> >> >> > >> > > > >
news:017E9FE7-9896-4503-8234-E5DF774813BE@.microsoft.com...
> >> >> > >> > > > > >I am posting this through the "Managed NewsGroup"
> >> >> > >> > > > > >
> >> >> > >> >
> >> >> > >
> >> >>
> >> >
> >
http://www.microsoft.com/sql/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.reportingsvcs
> >> >> > >> > > > > >
> >> >> > >> > > > > > and am still not getting an answer. I also have an
> >> >> > >> > > > > > MSDN
> >> >> > >> > subscription.
> >> >> > >> > > > > > Based upon the above postings - shouldn't I get a
> > response
> >> >> > >> > > > > > back?
> >> >> > >> > > > > >
> >> >> > >> > > > > > The workaround will not work for me as we have almost
a
> >> > 1,000
> >> >> > >> > reports that
> >> >> > >> > > > > > get exported to Excel. Yes - we only notced this
after
> >> > SP1.
> >> >> > >> > > > > >
> >> >> > >> > > > > > It is obvious that this is a bug (a pretty big one at
> >> > that).
> >> >> I
> >> >> > >> > don't want
> >> >> > >> > > > > > to get into a "p*ss*ng contest" about this but am
tired
> > of
> >> >> the
> >> >> > > back
> >> >> > >> > and
> >> >> > >> > > > > > forth
> >> >> > >> > > > > > about submitting a report case. It is simply a bug
> >> >> > >> > > > > > that
> >> >> > >> > > > > > is
> >> >> > >> > relatively
> >> >> > >> > > > > > simple
> >> >> > >> > > > > > to reproduce.
> >> >> > >> > > > > >
> >> >> > >> > > > > >
> >> >> > >> > > > > > "Bruce L-C [MVP]" wrote:
> >> >> > >> > > > > >
> >> >> > >> > > > > >> If you have universal you need to just post via a
> > managed
> >> >> > > newsgroup
> >> >> > >> > (if
> >> >> > >> > > > > >> you
> >> >> > >> > > > > >> haven't done this you post with a special fake email
> >> > address
> >> >> > > that
> >> >> > >> > you
> >> >> > >> > > > > >> have
> >> >> > >> > > > > >> registered in MSDN website and then someone from MS
> > will
> >> >> > >> > > > > >> answer
> >> >> > > and
> >> >> > >> > take
> >> >> > >> > > > > >> your repro case.
> >> >> > >> > > > > >>
> >> >> > >> > > > > >> I still think you have a misconception about this
> >> > newsgroup,
> >> >> > > that
> >> >> > >> > someone
> >> >> > >> > > > > >> from MS is watching every thread and that there
should
> > be
> >> >> some
> >> >> > > sort
> >> >> > >> > of
> >> >> > >> > > > > >> official statement from them. That is not how it
> >> >> > >> > > > > >> works.
> >> >> > >> > > > > >> If
> >> >> > > Brian
> >> >> > >> > happens
> >> >> > >> > > > > >> to
> >> >> > >> > > > > >> stop by then he might do something with it. I
noticed
> >> >> > >> > > > > >> that
> >> >> he
> >> >> > > first
> >> >> > >> > said
> >> >> > >> > > > > >> the
> >> >> > >> > > > > >> best thing was to get product support involved and
> >> >> > >> > > > > >> then
> >> >> > >> > > > > >> he
> >> >> > > mentions
> >> >> > >> > > > > >> posting.
> >> >> > >> > > > > >> So he went both ways with his answer. Posting might
> >> >> > >> > > > > >> get
> > a
> >> >> > > response,
> >> >> > >> > with
> >> >> > >> > > > > >> managed newsgroup or product support you will get a
> >> >> response.
> >> >> > >> > Otherwise
> >> >> > >> > > > > >> it
> >> >> > >> > > > > >> is peer.
> >> >> > >> > > > > >> --
> >> >> > >> > > > > >> Bruce Loehle-Conger
> >> >> > >> > > > > >> MVP SQL Server Reporting Services
> >> >> > >> > > > > >>
> >> >> > >> > > > > >> "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> > wrote
> >> > in
> >> >> > > message
> >> >> > >> > > > > >> news:OIsyY682EHA.1124@.tk2msftngp13.phx.gbl...
> >> >> > >> > > > > >> > Read the whole thread, Brian Welcker said "you
can
> >> >> > >> > > > > >> > post
> >> >> it
> >> >> > > here
> >> >> > >> > but
> >> >> > >> > > > > >> > for
> >> >> > >> > > > > >> us
> >> >> > >> > > > > >> > to repro, we would need more than a general
problem
> >> >> > > statement"
> >> >> > >> > etc.
> >> >> > >> > > > > >> > This
> >> >> > >> > > > > >> is
> >> >> > >> > > > > >> > exactly what I did way back (I found my old file
and
> >> >> posted
> >> >> > > it
> >> >> > >> > again).
> >> >> > >> > > > > >> > The
> >> >> > >> > > > > >> > same issue crops up, actually frequently, and an
MS
> >> >> employee
> >> >> > > does
> >> >> > >> > not
> >> >> > >> > > > > >> > say
> >> >> > >> > > > > >> > it's a bug, don't they know yet, or do they only
> >> >> > >> > > > > >> > tell
> >> >> people
> >> >> > > that
> >> >> > >> > > > > >> > contact
> >> >> > >> > > > > >> > the product support team?
> >> >> > >> > > > > >> >
> >> >> > >> > > > > >> > Our company has a universal MSDN subscription, and
I
> > am
> >> >> not
> >> >> > >> > hunting
> >> >> > >> > > > > >> > this
> >> >> > >> > > > > >> > issue, I bumped into the thread by accident, but
> > could
> >> > not
> >> >> > > keep
> >> >> > >> > quiet -
> >> >> > >> > > > > >> > something walks and quacks like a duck.
> >> >> > >> > > > > >> >
> >> >> > >> > > > > >> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com>
wrote
> > in
> >> >> > > message
> >> >> > >> > > > > >> > news:OSgQDD72EHA.3408@.tk2msftngp13.phx.gbl...
> >> >> > >> > > > > >> > > I just changed my view to see all messages and I
> > then
> >> >> see
> >> >> > > that
> >> >> > >> > this
> >> >> > >> > > > > >> > > is a
> >> >> > >> > > > > >> > > continuation of a posting from awhile back.
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > > It sounds like
> >> >> > >> > > > > >> > > 1. you have a work around.
> >> >> > >> > > > > >> > > 2. you want support from this newsgroup for your
> >> > problem
> >> >> > >> > > > > >> > > 3. you don't want to submit a support incident
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > > So, however much you feel like #2 should be
> > happening
> >> >> for
> >> >> > > you,
> >> >> > >> > that
> >> >> > >> > > > > >> isn't
> >> >> > >> > > > > >> > > how the newsgroup is setup to operate. You
either
> >> >> > >> > > > > >> > > need
> >> >> to
> >> >> > > open
> >> >> > >> > an
> >> >> > >> > > > > >> incident
> >> >> > >> > > > > >> > > or have an msdn subscription. The only people
that
> >> >> > >> > > > > >> > > get
> >> >> any
> >> >> > >> > support
> >> >> > >> > > > > >> > > other
> >> >> > >> > > > > >> > > than peer support is if you are an MSDN
> > subscription
> >> >> > >> > > > > >> > > holder
> >> >> > > in
> >> >> > >> > which
> >> >> > >> > > > > >> case
> >> >> > >> > > > > >> > > you this newsgroup is part of the managed
> > newsgroups.
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > > --
> >> >> > >> > > > > >> > > Bruce Loehle-Conger
> >> >> > >> > > > > >> > > MVP SQL Server Reporting Services
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > > "Chris Botha"
<chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> >> > wrote
> >> >> > >> > > > > >> > > in
> >> >> > >> > message
> >> >> > >> > > > > >> > > news:eed%23P262EHA.3244@.TK2MSFTNGP11.phx.gbl...
> >> >> > >> > > > > >> > > > If opening a support case would have fixed the
> >> > problem
> >> >> > > this
> >> >> > >> > month,
> >> >> > >> > > > > >> then
> >> >> > >> > > > > >> > it
> >> >> > >> > > > > >> > > > might have been worth the effort.
> >> >> > >> > > > > >> > > > I posted this problem just after the release
of
> > SP1
> >> >> > > (without
> >> >> > >> > SP1
> >> >> > >> > > > > >> > > > one
> >> >> > >> > > > > >> > > cannot
> >> >> > >> > > > > >> > > > export to Excel 2000), many others posted it
> > since
> >> >> then,
> >> >> > > and
> >> >> > >> > even
> >> >> > >> > > > > >> > > > if I
> >> >> > >> > > > > >> > > filed
> >> >> > >> > > > > >> > > > an incident then, there is no such thing as
SP2
> >> >> > >> > > > > >> > > > yet,
> >> >> and
> >> >> > > the
> >> >> > >> > client
> >> >> > >> > > > > >> > would
> >> >> > >> > > > > >> > > > have been off the roof by now.
> >> >> > >> > > > > >> > > > What I don't understand is why the MS guys
don't
> >> > just
> >> >> > > admit
> >> >> > >> > that it
> >> >> > >> > > > > >> > > > is
> >> >> > >> > > > > >> a
> >> >> > >> > > > > >> > > > problem and suggest a work-around or release a
> >> > hot-fix
> >> >> > >> > > > > >> > > > or
> >> >> > >> > > > > >> > > > something.
> >> >> > >> > > > > >> As
> >> >> > >> > > > > >> > I
> >> >> > >> > > > > >> > > > said, I found sizing the stuff above the table
> > like
> >> >> > > headers,
> >> >> > >> > other
> >> >> > >> > > > > >> text,
> >> >> > >> > > > > >> > > > etc, fixes the problem (haven't had any
> > complaints
> >> >> from
> >> >> > > the
> >> >> > >> > > > > >> > > > client),
> >> >> > >> > > > > >> and
> >> >> > >> > > > > >> > > the
> >> >> > >> > > > > >> > > > report that looses the last row, attached to
my
> >> > other
> >> >> > >> > posting, was
> >> >> > >> > > > > >> fixed
> >> >> > >> > > > > >> > > > like this and is running at the client.
> >> >> > >> > > > > >> > > >
> >> >> > >> > > > > >> > > > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com>
> >> >> > >> > > > > >> > > > wrote
> >> >> in
> >> >> > >> > message
> >> >> > >> > > > > >> > > > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> >> >> > >> > > > > >> > > > > I suggest opening up a support case. If it
is
> >> >> > >> > > > > >> > > > > a
> >> > bug
> >> >> > >> > > > > >> > > > > you
> >> >> > >> > don't get
> >> >> > >> > > > > >> > > charged.
> >> >> > >> > > > > >> > > > >
> >> >> > >> > > > > >> > > > > --
> >> >> > >> > > > > >> > > > > Bruce Loehle-Conger
> >> >> > >> > > > > >> > > > > MVP SQL Server Reporting Services
> >> >> > >> > > > > >> > > > >
> >> >> > >> > > > > >> > > > > "Chris Botha"
> >> >> > >> > > > > >> > > > > <chris_s_botha@.AT_h.o.t.m.a.i.l.com>
> >> >> > > wrote in
> >> >> > >> > > > > >> > > > > message
> >> >> > >> > > > > >> > > > >
news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> >> >> > >> > > > > >> > > > > > Hopefully by now you found a work-around,
> >> >> > >> > > > > >> > > > > > but
> >> >> > >> > > > > >> > > > > > in
> >> >> > >> > > > > >> > > > > > case
> >> >> > > you
> >> >> > >> > did
> >> >> > >> > > > > >> > > > > > not,
> >> >> > >> > > > > >> I
> >> >> > >> > > > > >> > > > found
> >> >> > >> > > > > >> > > > > > that if I re-arrange the stuff above the
> > table
> >> > a
> >> >> > > bit,
> >> >> > >> > like
> >> >> > >> > > > > >> headers
> >> >> > >> > > > > >> > > and
> >> >> > >> > > > > >> > > > > > other text, etc, it fixes the problem.
> >> >> > >> > > > > >> > > > > >
> >> >> > >> > > > > >> > > > > > "chanley54"
> >> > <chanley54@.discussions.microsoft.com>
> >> >> > > wrote
> >> >> > >> > in
> >> >> > >> > > > > >> > > > > > message
> >> >> > >> > > > > >> > > > > >
> >> >> > >> > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> >> >> > >> > > > > >> > > > > > > Hello,
> >> >> > >> > > > > >> > > > > > >
> >> >> > >> > > > > >> > > > > > > This question has been posted a few
times
> > and
> >> > is
> >> >> > >> > DEFINITELY A
> >> >> > >> > > > > >> SHOW
> >> >> > >> > > > > >> > > > > STOPPER
> >> >> > >> > > > > >> > > > > > > for Reporting Services.
> >> >> > >> > > > > >> > > > > > >
> >> >> > >> > > > > >> > > > > > > When exporting to Excel - the last row
can
> >> > turn
> >> >> up
> >> >> > >> > missing -
> >> >> > >> > > > > >> > > > > > > Why
> >> >> > >> > > > > >> > is
> >> >> > >> > > > > >> > > > > > > Microsoft not responding to this?
> >> >> > >> > > > > >> > > > > > >
> >> >> > >> > > > > >> > > > > >
> >> >> > >> > > > > >> > > > > >
> >> >> > >> > > > > >> > > > >
> >> >> > >> > > > > >> > > > >
> >> >> > >> > > > > >> > > >
> >> >> > >> > > > > >> > > >
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> > >
> >> >> > >> > > > > >> >
> >> >> > >> > > > > >> >
> >> >> > >> > > > > >>
> >> >> > >> > > > > >>
> >> >> > >> > > > > >>
> >> >> > >> > > > >
> >> >> > >> > > > >
> >> >> > >> > > > >
> >> >> > >> >
> >> >> > >> >
> >> >> > >> >
> >> >> > >
> >> >> > >
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>|||Hello Chris,
I have SP1 installed and I am having the same problem. You have to be
careful with the fix that you are suggesting, though. The report I am running
misses the last row only sometimes: It is being run approximately 500 times
per month, and it misses the last row about 2 to 3 times. In my report it is
easy to identify when the problem occurs because the rows are displayed in
pairs; in other words, you are supposed to be receiving two rows per ID. If
the last row is missing then users immediately call in order to ask for the
data in the missing row.
I was trying to find your sample report because I have not been able to
create one that fails everytime it is run. If you have such report then
please let me know because we can try installing SP2 in a test server and see
whether it solves the problem.
Regards,
Ricardo.
"Chris Botha" wrote:
> If opening a support case would have fixed the problem this month, then it
> might have been worth the effort.
> I posted this problem just after the release of SP1 (without SP1 one cannot
> export to Excel 2000), many others posted it since then, and even if I filed
> an incident then, there is no such thing as SP2 yet, and the client would
> have been off the roof by now.
> What I don't understand is why the MS guys don't just admit that it is a
> problem and suggest a work-around or release a hot-fix or something. As I
> said, I found sizing the stuff above the table like headers, other text,
> etc, fixes the problem (haven't had any complaints from the client), and the
> report that looses the last row, attached to my other posting, was fixed
> like this and is running at the client.
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > I suggest opening up a support case. If it is a bug you don't get charged.
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > > Hopefully by now you found a work-around, but in case you did not, I
> found
> > > that if I re-arrange the stuff above the table a bit, like headers and
> > > other text, etc, it fixes the problem.
> > >
> > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > > Hello,
> > > >
> > > > This question has been posted a few times and is DEFINITELY A SHOW
> > STOPPER
> > > > for Reporting Services.
> > > >
> > > > When exporting to Excel - the last row can turn up missing - Why is
> > > > Microsoft not responding to this?
> > > >
> > >
> > >
> >
> >
>
>|||I havent read all this thread but we have found a quick fix and that
is simply to put a blank textbox at the bottom of the report. This
fixes the problem and the text box does not get exported to excel.
Hope this works for you all.
Cheers
Vincent
"=?Utf-8?B?UmljYXJkbyBTYW1wZWk=?=" <RicardoSampei@.discussions.microsoft.com> wrote in message news:<9E52B424-87F9-42B0-851F-8BBF77DB5357@.microsoft.com>...
> Hello Chris,
> I have SP1 installed and I am having the same problem. You have to be
> careful with the fix that you are suggesting, though. The report I am running
> misses the last row only sometimes: It is being run approximately 500 times
> per month, and it misses the last row about 2 to 3 times. In my report it is
> easy to identify when the problem occurs because the rows are displayed in
> pairs; in other words, you are supposed to be receiving two rows per ID. If
> the last row is missing then users immediately call in order to ask for the
> data in the missing row.
> I was trying to find your sample report because I have not been able to
> create one that fails everytime it is run. If you have such report then
> please let me know because we can try installing SP2 in a test server and see
> whether it solves the problem.
> Regards,
> Ricardo.
> "Chris Botha" wrote:
> > If opening a support case would have fixed the problem this month, then it
> > might have been worth the effort.
> > I posted this problem just after the release of SP1 (without SP1 one cannot
> > export to Excel 2000), many others posted it since then, and even if I filed
> > an incident then, there is no such thing as SP2 yet, and the client would
> > have been off the roof by now.
> > What I don't understand is why the MS guys don't just admit that it is a
> > problem and suggest a work-around or release a hot-fix or something. As I
> > said, I found sizing the stuff above the table like headers, other text,
> > etc, fixes the problem (haven't had any complaints from the client), and the
> > report that looses the last row, attached to my other posting, was fixed
> > like this and is running at the client.
> >
> > "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
> > news:Ol#XvZ62EHA.1404@.TK2MSFTNGP11.phx.gbl...
> > > I suggest opening up a support case. If it is a bug you don't get charged.
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "Chris Botha" <chris_s_botha@.AT_h.o.t.m.a.i.l.com> wrote in message
> > > news:OoGx0Gn2EHA.1452@.TK2MSFTNGP11.phx.gbl...
> > > > Hopefully by now you found a work-around, but in case you did not, I
> > found
> > > > that if I re-arrange the stuff above the table a bit, like headers and
> > > > other text, etc, it fixes the problem.
> > > >
> > > > "chanley54" <chanley54@.discussions.microsoft.com> wrote in message
> > > > news:8DA86550-11B1-4696-8833-945064770F0F@.microsoft.com...
> > > > > Hello,
> > > > >
> > > > > This question has been posted a few times and is DEFINITELY A SHOW
> > > STOPPER
> > > > > for Reporting Services.
> > > > >
> > > > > When exporting to Excel - the last row can turn up missing - Why is
> > > > > Microsoft not responding to this?
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >