Macro Crash, Compile Problem

I have a rather lengthy macro. I understand the xlsb may be saved with a poor compile. This causes the macro to crash open opening.

The dance is - set security to not allow macros, open buggy xlsb, compile thru vba editor-debug, save/close , set security to allow, open xls and run.

This works, albeit the correction 'dance' takes a few minutes.

What I don't understand -

I purposely re-compile the macro prior to saving. Thus the xlsb is saved in allegedly error free state.

What happens after saving that is causing the xlsb macro to become 'de' compiled?

I've used the macro for about three years. 3-4 times I've taken the vba out and saved in macro free fashion. Then with clean xlsx I've added the vba back in. This has been done to 'clean' the code.

Thanks beforehand.

Thanks for the response.

a) The version created in was 2010. Currently running 2013.
b) The code is over 1000 lines.

I was anticipating a logical answer without specifics.

The question being, how can a xlsb be saved with no compile errors. But open opening, crashes because of compile errors???

Thanks again.

Thanks for the help. I agree, isolating a code error would be difficult.

I guess I am interested in knowing how a file becomes de-compiled after it is saved compiled.

Today it ran fine... go figure.