LinkBack Thread Tools Search this Thread Display Modes
Prev Previous Post   Next Post Next
  #2   Report Post  
Posted to microsoft.public.excel.programming
external usenet poster
 
Posts: 5,600
Default Excel 2007 bug caused by latest security patch KB973593

I just installed KB973593 (Nov 2009 not 2007), I cannot replicate the
problem you describe in 2007 SP2. I did this

Renamed a sheet to "myName"
populated the sheet with some data, actually three tables
put a Forms button on the sheet linked to a macro with

Application.Worksheets("myName").Protect

I ran the macro, I did not see any "bleeding"

I unprotected the sheet, copied the button to another sheet and tried again
(ie to protect a non-active sheet, again all fine. Intuitively I did not
expect a problem

Application.Worksheets("myName")
and
ActiveSheet
both return an object reference to a sheet. Once the reference is created
the syntax used to make it is irrelevant. The only thing that might be
different for some actions is whether the sheet is active or not (you didn't
say).

Try this -
Dim ws As Worksheet

Set ws = ActiveSheet
ws.Protect

and then
Set ws = Worksheets("worksheet name")
ws.Protect

Any difference ?

If you are still getting problems post back with full details how others may
replicate your scenario, including any particular data, formatting, shapes
on the sheet (if relevant), sheet name, and anything else that is
specifically required to reproduce your problem, eg some other code in your
macro. Obviously restrict to the minimum needed.

Regards,
Peter T


"Steve Smithfield" wrote in message
...
The security patch released on 11th November for Excel 2007 causes a
significant problem with Excel 2007 VBA applications.

The bug is related to protecting and unprotecting worksheets.

The statements ActiveSheet.Protect and ActiveSheet.Unprotect work fine.

However the statement Application.Worksheets("worksheet name").Protect
no longer works correctly. Whilst it protects the sheet (and the
unprotect statement unprotects the sheet) it causes content from sheets
which are not selected to bleed into the selected sheet. So if you run a
VBA macro, eg by pressing a button on a sheet, and the macro runs the
Application.Worksheets("worksheet name").Protect statement bits of
other non-selected sheets bleed in the currently selected sheet.

It's clearly an Excel bug as all content which has bleeded into the sheet
will vanish if you simply minimize the workbook and immediately maximize
it again. Or simply select another sheet then go back to the original
sheet.

ie it's cosmetic but you end up with a hell of a mess.

I have tested this with multiple Excel applications on Windows XP (Dell
desktop) and Vista. (Acer laptop).

I removed KB973593 and the problem vanished.

I re-installed KB973593 and the problem came back.

It's obviously possible to work around the problem, but when you have a
large number of applications it's a lot of work. Given protecting sheets
this way is very common and perfectly good practice I hope Microsoft can
issue a fix ASAP.



 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Recent security patch created problem in opening Excel Spreadsheet Vinoth Excel Discussion (Misc queries) 0 February 12th 10 01:32 PM
Excel Security Update KB973593 Todd Sorensen Excel Discussion (Misc queries) 1 January 26th 10 05:06 AM
Excel 2000 patch to view newer Excel versions (2003 and 2007) jmanuel Excel Discussion (Misc queries) 3 January 29th 09 05:11 PM
Can't open older .xls files after install 2007 patch sfleck Excel Discussion (Misc queries) 0 October 16th 07 07:54 PM
Latest Office patch de-registered EXCEL 2002 .Word/PP fine. Ideas BBTim Excel Discussion (Misc queries) 2 April 17th 06 09:44 PM


All times are GMT +1. The time now is 08:11 PM.

Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 ExcelBanter.
The comments are property of their posters.
 

About Us

"It's about Microsoft Excel"