A few observations around sharing violations in Excel 2007 on Windows 7,
when trying to save after modifying some data.

I'm not 100% certain #1 is related to W7, it may have existed in Vista too,
but I just discovered it today.

Of #2, I'm as good as certain that I've never seen it happen with Vista or
XP.


1) When I open (double-click) an XLS or XLSM file that contains unsigned
VBA macros, trying to save it causes a sharing violation. The macros just
have to be there, you don't have to try to run or edit them, just changing
some data and trying to close the window is enough.
"Save as" helps out.
Signing the macros fixes it.

2) When I open an XLS, XLSX or XLSM file that's located on the desktop,
trying to save it again causes a sharing violation error.
"Save as" helps out.
Move the file to the Documents folder or to some other user created folder
on disk, and the problem disappears.

3) If the save operation in either of the cases above is an auto-save,
Excel crashes (windows popup "ms excel has stopped working") and all
changes made so far are lost.
After Excel restarts (with or without allowing the system to search for a
solution online), I'm back in the original file as it was at the start.



BTW1: This is no Windows 7 RC or so, as a volume license and MSDN customer
I just got RTM a bit sooner than the stores.
The machine I've noticed the problem on is an upgrade from Vista.

BTW2: if there are any ms.public newsgroups for windows 7, under what name
did they hide them?

I'm experiencing a similar problem. Excel 2007. Win 7 RTM upgraded from
Vista. This started happening about a week ago.

In my case, however, I am working on a workbook with signed macros in some
cases, no macros in other cases.

Also, the folders I am using are user-created.

argh.

"Luc" wrote:

A few observations around sharing violations in Excel 2007 on Windows 7,
when trying to save after modifying some data.

I'm not 100% certain #1 is related to W7, it may have existed in Vista too,
but I just discovered it today.

Of #2, I'm as good as certain that I've never seen it happen with Vista or
XP.


1) When I open (double-click) an XLS or XLSM file that contains unsigned
VBA macros, trying to save it causes a sharing violation. The macros just
have to be there, you don't have to try to run or edit them, just changing
some data and trying to close the window is enough.
"Save as" helps out.
Signing the macros fixes it.

2) When I open an XLS, XLSX or XLSM file that's located on the desktop,
trying to save it again causes a sharing violation error.
"Save as" helps out.
Move the file to the Documents folder or to some other user created folder
on disk, and the problem disappears.

3) If the save operation in either of the cases above is an auto-save,
Excel crashes (windows popup "ms excel has stopped working") and all
changes made so far are lost.
After Excel restarts (with or without allowing the system to search for a
solution online), I'm back in the original file as it was at the start.



BTW1: This is no Windows 7 RC or so, as a volume license and MSDN customer
I just got RTM a bit sooner than the stores.
The machine I've noticed the problem on is an upgrade from Vista.

BTW2: if there are any ms.public newsgroups for windows 7, under what name
did they hide them?