Excel 2003 (8316.8221) screen corruption

[CSSLevel2]

Hi

Excel 2003 (11.8316.8221) SP3 on Windows XP

When the Excel starts it activates the first sheet in the workbook but shows
portions of the second and third sheet "bleeding" into the first sheet. This
is easily worked around by say minimising and maximising the workbook or
causing it to repaint in some other way. After the repaint the first sheet
shows correctly in full.

a) Has an update to Excel been issued which fixes this problem?
b) Can you think of a good workaround (given the details below)?

The workbook is a VBA application which has worked well for a number of
years. It has broken as described above since an update to Excel in
mid-October. The broken build is 11.8316.8221 SP3.

In the workbook open event a number of sheets are unprotected and then
protected (for drawing objects and scenarios). If this functionality is
commented out then the problem goes away. This behaviour looks shoddy and is
difficult to explain to the application's customers.

Thanks for your help.

 

[Peter T]

Sounds like you have been impacted by the recent KB973475 patch for Excel
2003 of 09-Nov-2009.

Try disabling ScreenUpdating at the start of your code and reset when done
Application.ScreenUpdating = False ' True

Could you report back if this has helped or not.

MS are aware problems with this patch and also KB973593 for Excel 2007.
Hopefully it won't be too long before the update is updated.

Regards,
Peter T

 

[Michael May]

Sounds like you have been impacted by the recent KB973475 patch for Excel
2003 of 09-Nov-2009.

Try disabling ScreenUpdating at the start of your code and reset when done
Application.ScreenUpdating = False ' True

Could you report back if this has helped or not.

MS are aware problems with this patch and also KB973593 for Excel 2007.
Hopefully it won't be too long before the update is updated.

Regards,
Peter T












- Show quoted text -

Thanks Peter. I did try suppressing the screen update but it did not
help. I was thinking of covering the workbook with a transparent
window or maybe minimising and maximising the workbook programatically
but I may wait to see if there is a fix on its way.

Is there any way to report the bug to Microsoft in the hope that it
gets fixed?

I'll post if I find a solution.

Mike

 

[Peter T]

Sounds like you have been impacted by the recent KB973475 patch for Excel
2003 of 09-Nov-2009.

Try disabling ScreenUpdating at the start of your code and reset when done
Application.ScreenUpdating = False ' True

Could you report back if this has helped or not.

MS are aware problems with this patch and also KB973593 for Excel 2007.
Hopefully it won't be too long before the update is updated.

Regards,
Peter T












- Show quoted text -

Thanks Peter. I did try suppressing the screen update but it did not
help. I was thinking of covering the workbook with a transparent
window or maybe minimising and maximising the workbook programatically
but I may wait to see if there is a fix on its way.

Is there any way to report the bug to Microsoft in the hope that it
gets fixed?

I'll post if I find a solution.

Mike
================================

As I mentioned before MS are aware of the issues, but if you have a support
contract with MS do get in contact as it's helpful in making them aware of
the impact.

Strange that workaround didn't work, particularly after doing
Application.ScreenUpdating = True

Another thing to try, when done
Dim wn As Window
' code
' all done
Set wn = ActiveWindow
Application.ScreenUpdating = False
wn.WindowState = xlMinimized
wn.WindowState = xlMaximized
Application.ScreenUpdating = True


If that doesn't work, enable screenupdating just before toggling the window.
Again please advise - looking for temporary workarounds!

And if that doesn't work could you give more details of what you are doing.

Regards,
Peter T

 

[Michael May]

Thanks Peter.  I did try suppressing the screen update but it did not
help.  I was thinking of covering the workbook with a transparent
window or maybe minimising and maximising the workbook programatically
but I may wait to see if there is a fix on its way.

Is there any way to report the bug to Microsoft in the hope that it
gets fixed?

I'll post if I find a solution.

Mike
================================

As I mentioned before MS are aware of the issues, but if you have a support
contract with MS do get in contact as it's helpful in making them aware of
the impact.

Strange that workaround didn't work, particularly after doing
Application.ScreenUpdating = True

Another thing to try, when done
Dim wn  As Window
' code
' all done
Set wn = ActiveWindow
Application.ScreenUpdating = False
wn.WindowState = xlMinimized
wn.WindowState = xlMaximized
Application.ScreenUpdating = True

If that doesn't work, enable screenupdating just before toggling the window.
Again please advise - looking for temporary workarounds!

And if that doesn't work could you give more details of what you are doing.

Regards,
Peter T- Hide quoted text -

- Show quoted text -

Thanks Peter. If I run that code (minimise-maximise) in the
Workbook_Open procedure, the corrupted screen problem still occurs.
However if I kick off a timer event in the Workbook_Open procedure and
then execute the the code in the event handler then the screen is
drawn properly. I am using a timeout of 2000 milliseconds but I don't
suppose the timeout period matters.

Thanks for your help.

 

[Peter T]

Thanks Peter. I did try suppressing the screen update but it did not
help. I was thinking of covering the workbook with a transparent
window or maybe minimising and maximising the workbook programatically
but I may wait to see if there is a fix on its way.

Is there any way to report the bug to Microsoft in the hope that it
gets fixed?

I'll post if I find a solution.

Mike
================================

As I mentioned before MS are aware of the issues, but if you have a
support
contract with MS do get in contact as it's helpful in making them aware of
the impact.

Strange that workaround didn't work, particularly after doing
Application.ScreenUpdating = True

Another thing to try, when done
Dim wn As Window
' code
' all done
Set wn = ActiveWindow
Application.ScreenUpdating = False
wn.WindowState = xlMinimized
wn.WindowState = xlMaximized
Application.ScreenUpdating = True

If that doesn't work, enable screenupdating just before toggling the
window.
Again please advise - looking for temporary workarounds!

And if that doesn't work could you give more details of what you are
doing.

Regards,
Peter T- Hide quoted text -

- Show quoted text -

Thanks Peter. If I run that code (minimise-maximise) in the
Workbook_Open procedure, the corrupted screen problem still occurs.
However if I kick off a timer event in the Workbook_Open procedure and
then execute the the code in the event handler then the screen is
drawn properly. I am using a timeout of 2000 milliseconds but I don't
suppose the timeout period matters.

Thanks for your help.

==============================================

Interesting, thanks for the feedback.

Could you briefly describe what the code does, and if it includes either
re-enabling screenupdating or redrawing Excel with min/restore when done to
fix.

Regards,
Peter T

 

[Michael May]

Thanks Peter.  If I run that code (minimise-maximise) in the
Workbook_Open procedure, the corrupted screen problem still occurs.
However if I kick off a timer event in the Workbook_Open procedure and
then execute the the code in the event handler then the screen is
drawn properly.  I am using a timeout of 2000 milliseconds but I don't
suppose the timeout period matters.

Thanks for your help.

==============================================

Interesting, thanks for the feedback.

Could you briefly describe what the code does, and if it includes either
re-enabling screenupdating or redrawing Excel with min/restore when done to
fix.

Regards,
Peter T

I used exactly the code that you proposed, reproduced below. My only
contribution was to execute in a Timer event handler (where the timer
is started at the end of the Workbook_Open procedure.

Dim wn As Window
Set wn = ActiveWindow
Application.ScreenUpdating = False
wn.WindowState = xlMinimized
wn.WindowState = xlMaximized
Application.ScreenUpdating = True

Mike

 

[Sujith Kumar]

Hi Peter,

This is valuable. I was really frustrated with this issue too. Do you have access to any microsoft links that admit to the issue?
It would be valuable to show to my boss.

Thanks,
Sujith



Peter T wrote:

Sounds like you have been impacted by the recent KB973475 patch for Excel2003
08-Dec-09

Sounds like you have been impacted by the recent KB973475 patch for Excel
2003 of 09-Nov-2009.

Try disabling ScreenUpdating at the start of your code and reset when done
Application.ScreenUpdating = False ' True

Could you report back if this has helped or not.

MS are aware problems with this patch and also KB973593 for Excel 2007.
Hopefully it will not be too long before the update is updated.

Regards,
Peter T

Previous Posts In This Thread:

Excel 2003 (8316.8221) screen corruption
Hi

Excel 2003 (11.8316.8221) SP3 on Windows XP

When the Excel starts it activates the first sheet in the workbook but shows
portions of the second and third sheet "bleeding" into the first sheet. This
is easily worked around by say minimising and maximising the workbook or
causing it to repaint in some other way. After the repaint the first sheet
shows correctly in full.

a) Has an update to Excel been issued which fixes this problem?
b) Can you think of a good workaround (given the details below)?

The workbook is a VBA application which has worked well for a number of
years. It has broken as described above since an update to Excel in
mid-October. The broken build is 11.8316.8221 SP3.

In the workbook open event a number of sheets are unprotected and then
protected (for drawing objects and scenarios). If this functionality is
commented out then the problem goes away. This behaviour looks shoddy and is
difficult to explain to the application's customers.

Thanks for your help.

Sounds like you have been impacted by the recent KB973475 patch for Excel2003
Sounds like you have been impacted by the recent KB973475 patch for Excel
2003 of 09-Nov-2009.

Try disabling ScreenUpdating at the start of your code and reset when done
Application.ScreenUpdating = False ' True

Could you report back if this has helped or not.

MS are aware problems with this patch and also KB973593 for Excel 2007.
Hopefully it will not be too long before the update is updated.

Regards,
Peter T

Thanks Peter. I did try suppressing the screen update but it did nothelp.
Thanks Peter. I did try suppressing the screen update but it did not
help. I was thinking of covering the workbook with a transparent
window or maybe minimising and maximising the workbook programatically
but I may wait to see if there is a fix on its way.

Is there any way to report the bug to Microsoft in the hope that it
gets fixed?

I will post if I find a solution.

Mike
================================

As I mentioned before MS are aware of the issues, but if you have a support
contract with MS do get in contact as it is helpful in making them aware of
the impact.

Strange that workaround did not work, particularly after doing
Application.ScreenUpdating = True

Another thing to try, when done
Dim wn As Window
' code
' all done
Set wn = ActiveWindow
Application.ScreenUpdating = False
wn.WindowState = xlMinimized
wn.WindowState = xlMaximized
Application.ScreenUpdating = True


If that does not work, enable screenupdating just before toggling the window.
Again please advise - looking for temporary workarounds!

And if that does not work could you give more details of what you are doing.

Regards,
Peter T

erisy andThanks Peter.
e
r
is
y and

Thanks Peter. I did try suppressing the screen update but it did not
help. I was thinking of covering the workbook with a transparent
window or maybe minimising and maximising the workbook programatically
but I may wait to see if there is a fix on its way.

Is there any way to report the bug to Microsoft in the hope that it
gets fixed?

I will post if I find a solution.

Mike

elonett.orofnis=3D=3D=3D=3D=3D=3D=3D=3Drtf
el
one
t
t.
or
of
n
is
=3D=3D=3D=3D=3D=3D=3D=3D
rt
f

7.butoktrhenydy=3D=3D=3D=3D=3D=3D=3D=3D=3Dof
7.
but
ok
t
r
hen
y
dy
=3D=3D=3D=3D=3D=3D=3D=3D=3D
of


Submitted via EggHeadCafe - Software Developer Portal of Choice
Join Lists with LINQ - SharePoint 2010
http://www.eggheadcafe.com/tutorial...6e-7d3fb7d38eca/join-lists-with-linq--sh.aspx

 

[Peter T]

Hello Sujith,

Microsoft released a Hotfix for the buggy KB973475 patch for Excel2003

download
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=978908&kbln=en-us

and another Hotfix for the similarly buggy KB973593 for Excel-2007

description
http://support.microsoft.com/default.aspx?scid=kb;EN-US;978522
download
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=978522&kbln=en-us

Regards,
Peter T