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?
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment