Other people that I work with are reporting bugs with macros and formulas.
We all use Excel daily for data processing (scientific usage). We have
alternative spreadsheet software available (Igor and Origin), but like the
Excel interface.
Uninstalling this update remedies these errors. Is there a better fix than
uninstalling the update?
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
I have developed several programs which uses XL VBA extensively, each in a
workboook with multiple sheets, many formulas and pivot tables. They have
been running successfully in the field for several years. After the recent
KB973475 update they all now fail with many of their displays to the end user
becoming corrupted. The display appears as a mixture of 2 or more sheets, one
of which usually contains a pivot table. This could be damage to the pivot
table, or merely failure of Excel to redraw the screen properly.
The corruption occurs after a pivot table is displayed and then VBA changes
a cell value on a different sheet in the same workbook, causing a
recalculation.
If KB973475 is uninstalled the fault goes away - the Excel file and the VBA
code does not get corrupted by this installation.
Has anyone else experienced this problem?
I definitely need an answer from Microsoft.
> I have developed several programs which uses XL VBA extensively, each in a
> workboook with multiple sheets, many formulas and pivot tables. They have
> been running successfully in the field for several years. After the recent
> KB973475 update they all now fail with many of their displays to the end user
> becoming corrupted. The display appears as a mixture of 2 or more sheets, one
> of which usually contains a pivot table. This could be damage to the pivot
> table, or merely failure of Excel to redraw the screen properly.
>
> The corruption occurs after a pivot table is displayed and then VBA changes
> a cell value on a different sheet in the same workbook, causing a
> recalculation.
> If KB973475 is uninstalled the fault goes away - the Excel file and the VBA
> code does not get corrupted by this installation.
>
> Has anyone else experienced this problem?
Yes, I have the same issue and so does a customer of mine. The fix is the same:
uninstall KB973475.
I have already opened a bug report with Microsoft about this and requested my
customer to do the same. If you have any support contract with MSFT, please
report this bug to them, it may help getting it fixed.
Regards,
Jan Karel Pieterse
Excel MVP
http://www.jkp-ads.com
Member of:
Professional Office Developer Association
www.proofficedev.com
I have already issued a bug report - so far have just received a brush-off
from the agent handling it for Microsoft, saying they don't have the
expertise! They seem reluctant to pass it on to Microsoft support.
"Jan Karel Pieterse" wrote:
> .
>
> They seem reluctant to pass it on to Microsoft support.
Well, luckily I did already. Hope they'll listen to me...
After we declined the Patch on WSUS the PCs still did have the patch.
However we have been able (fortunatelly even if Excel was running) to
remotely remove the Patch with the following command:
msiexec /package {90110409-6000-11D3-8CFE-0150048383C9} /uninstall
{E76CD647-C9A5-45BC-8B73-D0A7B61050A7} /quiet /norestart
Regards, Oliver
> However we have been able (fortunatelly even if Excel was running) to
> remotely remove the Patch with the following command:
>
> msiexec /package {90110409-6000-11D3-8CFE-0150048383C9} /uninstall
> {E76CD647-C9A5-45BC-8B73-D0A7B61050A7} /quiet /norestart
Thanks, very useful information!
Did you take the trouble of phoning Microsoft about the issue?
Please do so, so the chances increase they fix this!
You can Call 1-866-pcSafety for free, to report issues with security updates.
There seem to be two hotfixes to this problem:
KB973475 Excel 2003 hotfix package :
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=978908&kbln=en-us
KB973593 Excel 2007 hotfix package :
http://support.microsoft.com/default.aspx?scid=kb;EN-US;978522Regards,