stack memory error

Does the code fail on a specific line?

Just an FYI, the amount of RAM your computer has isnt as crucial as you might think at least for 32bit Excel. Excel x32 can only use 2GB of RAM per instance (not to be confused with per window or per workbook). Excel x64 can essentially utilize however much RAM the system has (there may be some upper limit but I am sure its absurdly high).

I dont see anything at a glance that would cause the issue. Typically I see that error when people try and store stuff in odd ways.

I would guess that the stack overflow error is because each time the change event is called, it makes a change to the spreadsheet, which calls the change event, which makes a change in the spreadsheet, which calls the change event, which...(I hope you get the idea). You essentially have an infinite loop/recursion that eventually will overflow the call stack.

I think this is the kind of scenario where you need to use the application.enableevents property to turn off events before the procedure makes changes, then re-enable events when the code is done: https://msdn.microsoft.com/en-us/VBA...property-excel

On edit: If I understand what the code is doing, it looks like it is basically conditional formatting/color of cells, and a SUM() function. I would not be surprised if this change event could be eliminated by using built in conditional formatting and a SUM(E:E) function in the appropriate cell.

Originally Posted by COURTTROOPER

I am going to contact our IT department to see if they can upgrade the software to 64 bit since we are running the Windows 64 bit.

I should clarify that switching to x64 is unlikely to be the right solution. You will be correcting the symptom, not the cause of the issue. 99% of people using Excel do NOT need x64, Microsoft still recommends x32 for most people. The reason being that many addins are still not compatible with x64 Excel (its getting better tho) and some VBA code (mostly those calling API's) would need to be updated to account for a 64bit version of Excel.

Could a 64bit version prevent memory related errors from coming up...sure. Does it actually correct the issue that caused those errors...no.

As mentioned by MrShorty (and I am embarrassed I overlooked it) you are running that code in an event, which also triggers itself. This likely causes issues. Its typical in an event like this to have the event code disable events, make the changes required, then re-enable events.

Going to 64bit to fix this would be like buying a new car because you dont know were the turn signal is on your old car. Another analogy; its like eating fried food and having high cholesterol so the dr puts you on medication. Does your cholesterol go down, sure...but if your still eating fried food you havent addressed the problem, only the symptoms.

EDIT: Another warning against x64 in this situation. You are raising the ceiling for which an issue can get to before causing an error. In the 32bit version you get an error and everything is "ok" (in that you can still use your file and try and correct the problem). In a 64bit version it may work for now, but without correcting the cause of the issue it may grow and grow until you get to the point that not only does it stop working but you also are unable to use the file or correct the issue.