Error:28 Out of Stack Space and I am out of options, What else can I do?

Breaking a program into multiple procedures can be an efficient way to program, provided the controlling procedure and any sub routines which call other procedures do not leave a trail of open procedures before accomplishing a task. Called procedures should do their individual tasks and then close, yielding back to the calling procedure as much as possible. If too many are left open while another procedure is called, you get the error because the memory stack can only handle so many variables and attributes at a time, So reviewing what your procedures are doing and seeing if you could yield back to the controlling procedure and let it make the call to the next procedure might solve your problem. I find that making a flow chart (block diagram) of the tasks and analyzing the logical steps helps in organizing how procedures interact.

Here are the Microsoft suggestions for managing potential causes:

1.Check that procedures are not nested too deeply.

2.Make sure recursive procedures terminate properly.

3.If local variables require more local variable space than is available, try declaring some variables at the module level. You can also declare all variables in the procedure static by preceding the Property, Sub, or Function keyword with Static. Or you can use the Static statement to declare individual static variables within procedures.

4.Redefine some of your fixed-length strings as variable-length strings, as fixed-length strings use more stack space than variable-length strings. You can also define the string at module level where it requires no stack space.

5.Check the number of nested DoEvents function calls, by using the Calls dialog box to view which procedures are active on the stack.

6.Make sure you did not cause an "event cascade" by triggering an event that calls an event procedure already on the stack. An event cascade is similar to an unterminated recursive procedure call, but it is less obvious, since the call is made by Visual Basic rather than an explicit call in the code. Use the Calls dialog box to view which procedures are active on the stack.

Originally Posted by JLGWhiz

Breaking a program into multiple procedures can be an efficient way to program, provided the controlling procedure and any sub routines which call other procedures do not leave a trail of open procedures before accomplishing a task.

Here are the Microsoft suggestions for managing potential causes:

I have read that many times over and over again Microsoft
But when I do that to split everything up in separate procedures then I will have millions and trillions of code lines

Only 1 colors has about 576460752303423488 Calculations on 59 cells

Imagine I want to use this with 58 colors more

Maybe I need to try it out and see what it will do

You only appear to have 5 different colour variations. Why not use Conditional Formatting and avoid VBA?

Originally Posted by gue2013

What is your intention on this application?

The intention is make a calculation with the Algo that I have created with this type of structure
I know what this Out of Stake Space mean Sir, but I don't know what I can change to prevent that happening without making allot of code lines
I know that the stack overflow has nothing to do with Codes size but would you type billions of code lines when you can do it with 1% of that number?..
the only problem I have is that I get this Stack Overflow....


You only appear to have 5 different colour variations. Why not use Conditional Formatting and avoid VBA?
The Excel will be very slow and also be very big..I mean really BIG
It can not calculate what I need Sir

Every change in 1 Cell the Module 1 has to run

Please don't quote whole posts -- it's just clutter.*If you are responding to a post out of sequence, limit quoted content to a few relevant lines that makes clear to whom and what you are responding

At some key points in your code, add break points. Then use View -> View Call Stack to see currently active procedure calls.
Ex: I added break point in your main procedure.
0.JPG

As you can see, there are more than one active process for each procedure.
Looks like none of the process terminated and it just keeps growing until stack error is reached.

This is what's causing your issue. Looking at your modules, you've defined very cell specific operation as individual subs.
Though I didn't follow through on entire dependency... looks like you are unnecessarily nesting procedures for each condition.

From your picture it isn't all that clear to me what your starting point is, and what your end goad of the code is.

You can do this"

Please Login or Register  to view this content.

But this is not recommended and will cause you problems.

Please Login or Register  to view this content.

The second set of code is how you have your code set up. The first set is the correct way to call macros. I cannot rewrite your macros for you because I do not understand what your are trying to do. But you need to rearrange the way you are calling the macros so that each one completes its task and then returns the control to the main macro. You can call one of the sub routines more than once from the main macro if need be, but leaving them open as illustrated in the second set above will definitely give you a stack overflow error.

To get a better understanding of the closing and yielding back principle, put these macros in a new workbook standard code module and use the F8 key to step through them. Watch how the yellow highlight moves from line to line and from macro to macro. Note the difference between set 1 and set 2. Do not run set 2 on automatic because it will be a perpetual loop and blow your memory stack.

See previous post.

This is far from perfect, but it will illustrate the technique better than my previous post. The object is to use the a control macro to call the Info-Data macros. By using a criteria to determine when to call each Info_Data macro, you can remove the call of the next Info_Data macro from the previous one and just let the control macro do the calling. That will then allow each Info-Data macro to do its task and then close, even though those are calling additional macros. So long as there is not a perpetual loop of calls or a string of macros left open, the error 28 should go away. Talke a look at the way I organized the code and see if you can use that or something like that to redo what you have. You should not have to use 4000 lines of code to do your analysis.

Please Login or Register  to view this content.