stake space

[RobcPettit]

Hi. I have a macro which kept throwing a 'out of stake space error'.
Ive read a bit here about stake space and confess I dont really
understand the beast. I found my error was down to an endless loop,
which Ive since fixed. My concern is this. The Data that the macro
analyzers, is fed live into the worksheet about every 1 secs. I cant
alter this as its an external software doing the feeding. My macro is
in the 'worksheet calculate'. Therefore the macro fires every 1 secs.
This is not a problem as such, because Iv put conditions in, which will
only add data to a modeless form when met. After saying that I also
added a counter at all possible condition, plus when conditions arnt
met, to see how many times the macro fires. The data coming in is from
Bacarat games, theres 5/6 rounds for each game. About 20 seconds
between rounds. So in a typical game the macro fires 100 times, not
necesarily doing anything, but firing all the same. Is this using stack
space. And if so If I left it running all the time, would I run out of
stack space. I have no static variables in my macro. Also theres
nothing in the macro that retains any values.(I think!). All values are
either added to worksheet or Form. Hope this makes sense.
Regards Robert

 

[NickHK]

If your macro only calculates and moves cell values around, you should be
OK, as long as your code has no leaks and/or infinite loops, as you have
found out.
If you have copy/paste of sheets, charts, graphics, etc you may run into
memory resource problem.

NickHK

 

[RobcPettit]

Thanks for the reply. Im not using charts/graphics or copy/paste so
should be ok there. Is there any line of code I can add to show stack
space?. Thanks again.
Regards Robert

 

[NickHK]

Whilst debugging, you can View>Call Stack.
Whilst running, the VBE does not exposes anything natively, but there
probably are ways using additional code. Pretty hairy unless you really want
to go there.
If you just want to see the memory usage, there the various
Application.MemoryXXX function, although they never seem very accurate.

NickHK

 

[RobcPettit]

Thanks NickHK, Ill stick to debugging. Maybe if the error comes up
again, I will look further, but until then...... Thanks for taking the
time to reply.
Regards Robert