Macros stop working, supposed to find next empty cell in column and label...

Hi Everyone, I hope this is the right area and format to post.

Bascially, a company i started doing work for has excel files they use to keep statistic data in, and every time it opens it runs a couple macros that go to the bottom of a column and label the next empty cell as either NextWeek or NextMonth, and then creates a label for the previous 13 positions on every column like "A_Data" or "AB_Data" depending on which column. Finally, there are graphs with their own worksheet tabs at the bottom that update automatically with the data because they point their data to the labels "AB_Data" for the x-axis.

HOWEVER, even though we use the same template for about 200 different files, about 1 in 15 goes awry and it just stops updating the labels, and I don't know enough about excel macros to figure out why they're breaking!? AAARgghh..

Anyway, I'm going to include an example of a working one, and a non working one. In the non working one (example 1) it labels A473 as NextWeek but it's supposed to label A482 as such.

Any and all help is super appreciated! I'm dying trying to just figure out what it is that triggers these to break, let alone figure out a fix, but I'm spread pretty thin and I'm just helping out in the area since no one else here has a clue.

-E

What you are calling a "Label" is usually referred to as a "Named Range". It took me a while to figure out what you meant.

In the workbook that is not working, columns Z:AL should be shifted one column to the right to AA:AM. This would line up with the same columns in the workbook that does work. If you shift the columns over by one, the named ranges seem to update properly. My guess is someone deleted a column to the left of AA and shifted everything to the left.

One other item to note; within the SetRegions procedure (where the Named Ranges are updated), there is an error handler at the end called Process_Error:. The error handler only exits the procedure. While this is expedient, it doesn't tell the user there was a problem. So basically, it was "hiding" the error. Maybe change it to this so at least it shows a message that there is a problem should it happen again.

Please Login or Register  to view this content.

Thank begonias!

And that's good to know that it can be changed to show the error. You're awesome!

Ahh I see, thank you, will do next time.