Error when running one of 5 Macros in new version of Excel

Hello all,

Never had this problem before. I recently switched to a 64bit version of excel, and one of the 5 macros that I use now hit's me with out of stack space error 28. When I first made the switch, the error would pop up early in the macro, now it's toward the end of the macro.

Any thoughts about what I need to do? The first Bold Italic UL is where the macro was failing when I first switched, now it fails at the second one. I removed some specific names from the second part of the macro, so that's not random unneeded space.

TIA

Please Login or Register  to view this content.

I don't think it is good practice to call the subroutine AND the GoSub routine the same name (Gray). It is, at best, confusing and, at worst, perhaps problematic.

Took me a while to find out what combination of values to put in such that the row did NOT turn gray, but got there in the end.

I'd put some debug statements in, something like the following, to try to track where the routine fails and what the key fields are at the time.

Please Login or Register  to view this content.

Originally Posted by TMS

I don't think it is good practice to call the subroutine AND the GoSub routine the same name (Gray).....

Attachment 790408

No luck here either. Now it's ending early in the run like it did before.

Please:

1. Add code tags to your original post
2. Do NOT quote whole posts in your replies; it is just clutter
3. Post a sample workbook with typical data that demonstrates the problem
4. The attachment is invalid so I don't know what that says.

I can only help you if there is something to work on. Otherwise it is just guesswork.

Thanks for adding the code tags and removing the clutter.

A picture is still not very helpful. I can get get your code to run with a small file I have created and I can get diagnostic information from it. However, that clearly does not reflect the issue that you have.

I have 32 bit Excel so it does not reflect your environment. But, if your data runs or fails for me, it will send us along one path or another. If it works for me but not for you, it is possibly the environment (64 bit). If it does not work for me, it is possibly the data. So, "possibilities" that need to be explored.

Yes, I'm assuming it has to do with the 64 bit version. I wasn't sure if there were any way to fix this.

Still an assumption. I can't see anything obvious in the code that would be an issue. But no way I can help you to eliminate it.

That said, as long as I have been programming in Excel with VBA, I have never used GoSub, and never will. I know nothing of its merits or disadvantages but it doesn't fit with the way I code. Given that you don't use Return from the GoSub, you probably don't need GoSub anyway and could get away with a simple GoTo.

I would be inclined to make the Gray (GoSub line) into a separate function and pass it the row number.

My take on how this could be coded. In my view, this is taking a more positive approach to which rows to colour. Obviously you would need to check it highlights the correct entries for the correct conditions.

Please Login or Register  to view this content.