R
Ron West
Suppose I have a command button on a worksheet with a macro assigned to it,
and change the scope of the macro so that it is no longer accessible by the
command button.
By any sensible definition of compilation this change should be detected
when compiling the worksheet, but it is NOT detected by Debug->Compile
VBAProject and liable to only be found at run-time by a user or client after
sign-off.
Microsoft - please fix for SP2...!
----------------
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.
http://www.microsoft.com/office/com...2d47c27&dg=microsoft.public.excel.crashesgpfs
and change the scope of the macro so that it is no longer accessible by the
command button.
By any sensible definition of compilation this change should be detected
when compiling the worksheet, but it is NOT detected by Debug->Compile
VBAProject and liable to only be found at run-time by a user or client after
sign-off.
Microsoft - please fix for SP2...!
----------------
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.
http://www.microsoft.com/office/com...2d47c27&dg=microsoft.public.excel.crashesgpfs