Hello,

I know this topic has been addressed many times in this group, but I
can't seem to find an answer to my particular case. Running Excel97.

I have a fairly small workbook, approx. 200Kb, containing 9 worksheets
with a few formulas on each sheet - nothing very complicated. It is a
Source to another workbook. The main macro opens the Target workbook,
adds a few links to the Source, then closes the Target. Up until a
short time ago, everything was working fine - suddenly I'm getting the
dreaded "Out of memory" message when trying to edit any macro in the
module. I can export the module, but I can't delete it. Also, the
Target file is remaining visible in the Project Explorer, even though
it's closed. Rob Bovey's VBA Code cleaner doesn't appear to function
normally in this situation, it just creates a duplicate module in the
same project (which I can delete).

I'm running out of ideas, any help would be greatly appreciated -
thank you.

Regards,

Dave

Dave, I don't understand your "can't delete" statement about the code module.
What prevents the deletion? On the out of memory issue, have you looked for
recursive calls in your code, where it keeps calling itself, infinite calc
routines due to auto calc procedures, etc. If you have your code in sub
routines, you could run them one at a time to find the cuplrit, else, just
delete all the code in the procedure that produces the error message. You
don't have to delete the module, just the code.

"Dave Unger" wrote:

Hello,

I know this topic has been addressed many times in this group, but I
can't seem to find an answer to my particular case. Running Excel97.

I have a fairly small workbook, approx. 200Kb, containing 9 worksheets
with a few formulas on each sheet - nothing very complicated. It is a
Source to another workbook. The main macro opens the Target workbook,
adds a few links to the Source, then closes the Target. Up until a
short time ago, everything was working fine - suddenly I'm getting the
dreaded "Out of memory" message when trying to edit any macro in the
module. I can export the module, but I can't delete it. Also, the
Target file is remaining visible in the Project Explorer, even though
it's closed. Rob Bovey's VBA Code cleaner doesn't appear to function
normally in this situation, it just creates a duplicate module in the
same project (which I can delete).

I'm running out of ideas, any help would be greatly appreciated -
thank you.

Regards,

Dave

Hi JLGWhiz

I don't think this is a coding issue, the macros are not running when
I get the "out of memory" message. It pops up as soon as I try to
edit or delete any of the individual procedures while in the VBE, not
while the macros are running. It also appears if I try to delete the
entire module, which is what prevents me from doing so. Some
corruption in the module must be be affecting the VB editor. All I'm
able to do is export the module, and that looks OK.

Thanks for your reply

regards,

Dave

thatOn May 30, 8:26 am, JLGWhiz
wrote:
Dave, I don't understand your "can't delete" statement about the code module.
What prevents the deletion? On the out of memory issue, have you looked for
recursive calls in your code, where it keeps calling itself, infinite calc
routines due to auto calc procedures, etc. If you have your code in sub
routines, you could run them one at a time to find the cuplrit, else, just
delete all the code in the procedure that produces the error message. You
don't have to delete the module, just the code.



"Dave Unger" wrote:
Hello,

I know this topic has been addressed many times in this group, but I
can't seem to find an answer to my particular case. Running Excel97.

I have a fairly small workbook, approx. 200Kb, containing 9 worksheets
with a few formulas on each sheet - nothing very complicated. It is a
Source to another workbook. The main macro opens the Target workbook,
adds a few links to the Source, then closes the Target. Up until a
short time ago, everything was working fine - suddenly I'm getting the
dreaded "Out of memory" message when trying to edit any macro in the
module. I can export the module, but I can't delete it. Also, the
Target file is remaining visible in the Project Explorer, even though
it's closed. Rob Bovey's VBA Code cleaner doesn't appear to function
normally in this situation, it just creates a duplicate module in the
same project (which I can delete).

I'm running out of ideas, any help would be greatly appreciated -
thank you.

Regards,

Dave- Hide quoted text -

- Show quoted text -

Is the code in a standard module, like Module 1, or is it behind a sheet or
ThisWorkbook? If it is in a standard module, I couldn't begin to guess what
is wrong, but if it is in a sheet or ThisWorkbook module, I would suspect an
event code is giving you the business. If you have any event codes, Maybe
copy them to Notebook to save them, then delete them until you find the
booger.

"Dave Unger" wrote:

Hi JLGWhiz

I don't think this is a coding issue, the macros are not running when
I get the "out of memory" message. It pops up as soon as I try to
edit or delete any of the individual procedures while in the VBE, not
while the macros are running. It also appears if I try to delete the
entire module, which is what prevents me from doing so. Some
corruption in the module must be be affecting the VB editor. All I'm
able to do is export the module, and that looks OK.

Thanks for your reply

regards,

Dave

thatOn May 30, 8:26 am, JLGWhiz
wrote:
Dave, I don't understand your "can't delete" statement about the code module.
What prevents the deletion? On the out of memory issue, have you looked for
recursive calls in your code, where it keeps calling itself, infinite calc
routines due to auto calc procedures, etc. If you have your code in sub
routines, you could run them one at a time to find the cuplrit, else, just
delete all the code in the procedure that produces the error message. You
don't have to delete the module, just the code.



"Dave Unger" wrote:
Hello,

I know this topic has been addressed many times in this group, but I
can't seem to find an answer to my particular case. Running Excel97.

I have a fairly small workbook, approx. 200Kb, containing 9 worksheets
with a few formulas on each sheet - nothing very complicated. It is a
Source to another workbook. The main macro opens the Target workbook,
adds a few links to the Source, then closes the Target. Up until a
short time ago, everything was working fine - suddenly I'm getting the
dreaded "Out of memory" message when trying to edit any macro in the
module. I can export the module, but I can't delete it. Also, the
Target file is remaining visible in the Project Explorer, even though
it's closed. Rob Bovey's VBA Code cleaner doesn't appear to function
normally in this situation, it just creates a duplicate module in the
same project (which I can delete).

I'm running out of ideas, any help would be greatly appreciated -
thank you.

Regards,

Dave- Hide quoted text -

- Show quoted text -

Something has to be running somewhere for it to give the out of memory
message. Finding what it is that runs and what causes it to run is the trick.

"Dave Unger" wrote:

Hi JLGWhiz

I don't think this is a coding issue, the macros are not running when
I get the "out of memory" message. It pops up as soon as I try to
edit or delete any of the individual procedures while in the VBE, not
while the macros are running. It also appears if I try to delete the
entire module, which is what prevents me from doing so. Some
corruption in the module must be be affecting the VB editor. All I'm
able to do is export the module, and that looks OK.

Thanks for your reply

regards,

Dave

thatOn May 30, 8:26 am, JLGWhiz
wrote:
Dave, I don't understand your "can't delete" statement about the code module.
What prevents the deletion? On the out of memory issue, have you looked for
recursive calls in your code, where it keeps calling itself, infinite calc
routines due to auto calc procedures, etc. If you have your code in sub
routines, you could run them one at a time to find the cuplrit, else, just
delete all the code in the procedure that produces the error message. You
don't have to delete the module, just the code.



"Dave Unger" wrote:
Hello,

I know this topic has been addressed many times in this group, but I
can't seem to find an answer to my particular case. Running Excel97.

I have a fairly small workbook, approx. 200Kb, containing 9 worksheets
with a few formulas on each sheet - nothing very complicated. It is a
Source to another workbook. The main macro opens the Target workbook,
adds a few links to the Source, then closes the Target. Up until a
short time ago, everything was working fine - suddenly I'm getting the
dreaded "Out of memory" message when trying to edit any macro in the
module. I can export the module, but I can't delete it. Also, the
Target file is remaining visible in the Project Explorer, even though
it's closed. Rob Bovey's VBA Code cleaner doesn't appear to function
normally in this situation, it just creates a duplicate module in the
same project (which I can delete).

I'm running out of ideas, any help would be greatly appreciated -
thank you.

Regards,

Dave- Hide quoted text -

- Show quoted text -

HI JLGWhiz

Things really started getting weird, it got so that I couldn't assign
a macro to a worksheet button without Excel shutting down. So, as a
last resort I un-installed, then re-installed Excel. Guess what - all
my problems went away! Some application file must have got corrupted
somehow.

Anyway, it's working now, finally. Appreciate your interest.&
suggestions.

regards,

Dave


On May 30, 11:59 am, JLGWhiz
wrote:
Something has to be running somewhere for it to give the out of memory
message. Finding what it is that runs and what causes it to run is the trick.



"Dave Unger" wrote:
Hi JLGWhiz

I don't think this is a coding issue, the macros are not running when
I get the "out of memory" message. It pops up as soon as I try to
edit or delete any of the individual procedures while in the VBE, not
while the macros are running. It also appears if I try to delete the
entire module, which is what prevents me from doing so. Some
corruption in the module must be be affecting the VB editor. All I'm
able to do is export the module, and that looks OK.

Thanks for your reply

regards,

Dave

thatOn May 30, 8:26 am, JLGWhiz
wrote:
Dave, I don't understand your "can't delete" statement about the code module.
What prevents the deletion? On the out of memory issue, have you looked for
recursive calls in your code, where it keeps calling itself, infinite calc
routines due to auto calc procedures, etc. If you have your code in sub
routines, you could run them one at a time to find the cuplrit, else, just
delete all the code in the procedure that produces the error message. You
don't have to delete the module, just the code.

"Dave Unger" wrote:
Hello,

I know this topic has been addressed many times in this group, but I
can't seem to find an answer to my particular case. Running Excel97.

I have a fairly small workbook, approx. 200Kb, containing 9 worksheets
with a few formulas on each sheet - nothing very complicated. It is a
Source to another workbook. The main macro opens the Target workbook,
adds a few links to the Source, then closes the Target. Up until a
short time ago, everything was working fine - suddenly I'm getting the
dreaded "Out of memory" message when trying to edit any macro in the
module. I can export the module, but I can't delete it. Also, the
Target file is remaining visible in the Project Explorer, even though
it's closed. Rob Bovey's VBA Code cleaner doesn't appear to function
normally in this situation, it just creates a duplicate module in the
same project (which I can delete).

I'm running out of ideas, any help would be greatly appreciated -
thank you.

Regards,

Dave- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -