J
J Streger
I just received my copy of Office 2007. Pop the clutch, give the tranny a
spin and *crash*, my sheet doesn't work as intended. OK I expected as much.
So I start to step through the code and get to
Sheets(name).shapes(Shapename).Delete and to my shock, I am kicked out of
debug mode. (You know that message that says you cannot step through the code
anymore). Now I am used to this with Sheet deletions, but now shapes too? Did
they use a sub-par debugger this go around? And is there any way to get
around this, as debugging around this problem is a royal pain in the you know
where? I tested in 2003 and I can step through shape deletions fine.
It actually seems that the shapes collection took a hit of change, since I
noticed my sheet, which uses a lot of shapes as buttons, has VBA controls
getting renamed and moved as shapes. *sigh* So any solution to stopping this
debug kicking issue?
spin and *crash*, my sheet doesn't work as intended. OK I expected as much.
So I start to step through the code and get to
Sheets(name).shapes(Shapename).Delete and to my shock, I am kicked out of
debug mode. (You know that message that says you cannot step through the code
anymore). Now I am used to this with Sheet deletions, but now shapes too? Did
they use a sub-par debugger this go around? And is there any way to get
around this, as debugging around this problem is a royal pain in the you know
where? I tested in 2003 and I can step through shape deletions fine.
It actually seems that the shapes collection took a hit of change, since I
noticed my sheet, which uses a lot of shapes as buttons, has VBA controls
getting renamed and moved as shapes. *sigh* So any solution to stopping this
debug kicking issue?