Does closing modules increase stability?

[Don Wiss]

I have a workbook with lots of code. Usually I leave all of the modules
open. Sometimes the workbook blows up Excel. I will try closing all the
modules, but does it make a difference?

Don <www.donwiss.com> (e-mail link at home page bottom).

 

[FSt1]

hi
what do you mean by "leave all the modules open" and "close all modules"???
i do have some experence with vb and macros but this is terminology i
haven't heard before. please clairfy.

Regards
FSt1

 

[Dana DeLouis]

what do you mean by "leave all the modules open" and "close all
modules"???

Hi. Select somewhere in a code module, and keep hitting Ctrl+F4 until
all the modules are closed.
I have collected a library of stuff in my Personal.xls file.
Since I don't often edit them, I try to remember to keep all of these
modules closed.
I have not read anything where this is a problem, but I would guess that
it might help a little, whatever that might mean.

I have heard here in the newsgroups that code with about 64k of lines
will cause a crash. If you have a lot of lines of code, perhaps break
them up into more modules. (Just guessing here of course)

- - -
Dana DeLouis

 

[FSt1]

hi
Ctrl+F4 closes the active window...not the macro. this is my confusion. you
can close all the active window you want in the vb editor but when you call
the macro in code.....guess what runs. this is my confusion. what constitutes
a "closed" macro?
MVPs.....help!!!!!

Regards
FSt1

 

[FSt1]

hi
it 2am in atlanta. crashing here. will check post tommorrow.
regards
FSt1

 

[Charlie]

No. Not a bit of difference. You don't really "open" and "close" the
modules. You are simply opening and closing the window that lets you view
and edit the code. The code is always there even when the window is closed.
Like when you hide a row.

Whether or not the code is visible is irrelevant to whether or not it is
running. Just having the code in sight does not necessarily mean it is
running. Usually it is not. It MAY be run if you click on a control or in a
cell that fires an event, and the event happens to call the particular Sub
that is in view in the editor. You can set a breakpoint in the sub to catch
when it gets executed and see what I mean.

No, I never bother closing the modules. (Unless I'm done with development).

 

[Don Wiss]

Ctrl+F4 closes the active window...not the macro. this is my confusion. you
can close all the active window you want in the vb editor but when you call
the macro in code.....guess what runs. this is my confusion. what constitutes
a "closed" macro?
MVPs.....help!!!!!

Boy, do I hate top posting. It is done by people that are too lazy to
properly edit down what they are replying to and put the followup into the
standard Usenet question-answer format.

Maybe because of the top posting you didn't read my OP. I clearly referred
to closing modules. Never did I use the word macros. And of course the
macros will still run whether the module is open or not.

Don <www.donwiss.com> (e-mail link at home page bottom).

 

[Gord Dibben]

Don

You can bottom-post until the cows come home and most won't care, but the
accepted practice in these Excel news groups has always been top-posting.

Branding all top-posters as lazy is insulting and arrogant and should get
you on a few plonk lists.

PLONK


Gord Dibben MS Excel MVP

 

[Gary Keramidas]

I don't know anybody that starts reading a thread at the bottom, so bottom
posting is really annoying. I start with the first thread and follow the
posts. when I come to one, 10 posts down, and it's a bottom post, it's
really aggravating to have to scroll through the 10 posts I just read to see
the reply.

that's my opinion, anyway.