More problems with Excel VBA

[wackywoo105]

A workbook that has been running fine for years decided to fall over on Chr(13), which I fixed with vbCrLf (which I use these days but didn't a long time ago).

The following day it started crashing again on Thisworkbook.activate.

These are complete crashes, not vba end/debug errors.

I found the issues by adding stop and stepping through the code until the crash.

Why would something like this just suddenly start acting up? Some of the code is around 10 years old.

I'm getting fed up of putting out one fire only to encounter another soon after.

 

[Peter_SSs]

If it is just this one workbook crashing then possibly it has become corrupted. Would you be able to revert to a recent 'good' back-up and go from there?

BTW, I suggest that you update your Account details (or click your user name at the top right of the forum) so helpers always know what Excel version(s) & platform(s) you are using as the best solution often varies by version. (Don’t forget to scroll down & ‘Save’)

 

[jkpieterse]

Does chr(13) give you a compile error by any chance?
Two things to try:

1. From the VBA Editor, choose Tools, References. Do any show "MISSING"?
2. Try cleaning the VBA code by exporting all modules, deleting them and importing them again.