Sub Total function is broken since the latest Office patch

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am the onsite tech support person at a major insurance company. We
discovered the latest patch has broken the Sub Total function in Excel. We
are exporting data from PeopleSoft into Excel. We have several columns in
this data, one of them being Product ID and another column is Amount which
displays dollar amounts in the format 1,111.11. After sorting when we see
there is a break in the data where the Product ID changes, we insert a line
and perform the Sub Total function to seperate those amounts by Product ID
and give us totals per Product ID. That has stopped working now since
applying the patch. If we back out the patch we regain the functionality.
Hopefully Microsoft knows about this and will release a fix for this soon.
 
Jan Karel Pieterse said:
Hi Techguy,


What version of Office are we talking here?
Have you searched the MS Knowledge base about this problem?


I have not searched the knowledge base only because of the fact this patch
was just released and figured it may be a bug that Microsoft may not be aware
of yet. I thought by posting here someone might have run into it and has come
up with a workaround or fix for this.
 
Hi Techguy,
I thought by posting here someone might have run into it and has come
up with a workaround or fix for this.

Good point. I didn't know of the problem. I have forwarded your message
to Microsoft. If anything gets back I'll let you know.

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
 
Hey Techguy,

Is there any chance that you could email to me a worksheet that reproduces
the problem? Obviously, this should not contain any confidential data, just
a simple worksheet where the Excel folks can see a repro of the issue.

I'm at mikefos[at]microsoft.com

Thanks,
Michael Fosmire
Excel MVP Lead

This posting is provided AS IS with no warranties, and confers no rights.
 
Hi Mike,
Is there any chance that you could email to me a worksheet that reproduces
the problem? Obviously, this should not contain any confidential data, just
a simple worksheet where the Excel folks can see a repro of the issue.

Thanks for jumping in, much appreciated.

Regards,

Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
 
Nice to see you in at the sharp end Mike, welcome :-)

--
Regards
Ken....................... Microsoft MVP - Excel
Sys Spec - Win XP Pro / XL 97/00/02/03

------------------------------­------------------------------­----------------
It's easier to beg forgiveness than ask permission :-)
------------------------------­------------------------------­----------------



Michael Fosmire said:
Hey Techguy,

Is there any chance that you could email to me a worksheet that reproduces
the problem? Obviously, this should not contain any confidential data,
just a simple worksheet where the Excel folks can see a repro of the
issue.

I'm at mikefos[at]microsoft.com

Thanks,
Michael Fosmire
Excel MVP Lead

This posting is provided AS IS with no warranties, and confers no rights.

Techguy said:
I have not searched the knowledge base only because of the fact this
patch
was just released and figured it may be a bug that Microsoft may not be
aware
of yet. I thought by posting here someone might have run into it and has
come
up with a workaround or fix for this.
 
So I haven't seen anything in my inbox. Should I assume that this issue has
been resolved? If not, please let me know!

Thanks,
Michael Fosmire
Excel MVP Lead

This posting is provided AS IS with no warranties, and confers no rights.


Michael Fosmire said:
Hey Techguy,

Is there any chance that you could email to me a worksheet that reproduces
the problem? Obviously, this should not contain any confidential data,
just a simple worksheet where the Excel folks can see a repro of the
issue.

I'm at mikefos[at]microsoft.com

Thanks,
Michael Fosmire
Excel MVP Lead

This posting is provided AS IS with no warranties, and confers no rights.

Techguy said:
I have not searched the knowledge base only because of the fact this
patch
was just released and figured it may be a bug that Microsoft may not be
aware
of yet. I thought by posting here someone might have run into it and has
come
up with a workaround or fix for this.
 
Back
Top