Help with vba macro crash

Does the code break?

Is all the code in the sheet module? Everything except the Change event should be in a standard module.

I think Multiclass could be replaced with something like this:

Please Login or Register  to view this content.

... and the other code could be similarly simplified.

I am not sure what it means for the code to "break", but if you mean whether or not it displays some sort of error/warning, then - no, it runs flawlessly, executes to the end and then excel just closes.

Actually I've put all the code on one sheet (Sheet1) is that a problem?

And thank you, that looks much simpler, I didn't know the .find method even existed before this. :D
I shall rewrite it and see what happens.

EDIT: OK, so I've rewritten the subroutines "References" and "Multiclass", at first they both worked fine but when I basically ran the third "if" from the "Worksheet_Change" sub it began to crash every time I used any of the subs, afterwards.

Please Login or Register  to view this content.

Actually I've put all the code on one sheet (Sheet1) is that a problem?

Put the change event code in the sheet module and everyhing else in a standard module.

When you say "crash", you mean Excel closes?

Yes, I thought I have mentioned that?

I can tell the entire thing works, because it fills the correct values and a second after excel just closes itself, just like that.

I am not sure what it means for the code to "break", but if you mean whether or not it displays some sort of error/warning, then - no, it runs flawlessly, executes to the end and then excel just closes.

I am not sure if it matters, but I would like to stress that it DOES execute to the end and AFTER it closes. Although I am not sure if that's because the problem is within the end of the procedure of whether it is processor lag.

By code breaking, I mean it stops executing and the VBE takes you to the code with the offending line highlighted (or gives you the option of doing so if you select Debug).

You say your code runs to the end; how do you know that?

You could set several breakpoints in your code, including at the last line (End Sub) of the Change event; if you don't get there, it didn't finish executing. In VBE options, you could set error handling to break on all errors.

I do note that you have a long If/ElseIf statement to set ranges, but nothing to test that they are actually set (there is no Else clause).

If you're not already familiar, now would be a good time to read http://www.cpearson.com/excel/debug.htm

You're welcome.

There is nothing, nothing that will improve your coding skill like debugging your own code.