Hi everyone.
I've lately noticed an issue with my Personal.xlsb workbook becoming corrupted when I create a macro that utilizes userforms. I noticed this tends to happen when I'm testing the code, typically after stopping the macro with the blue stop button on the toolbar.
Typically once the data is corrupted, I can open Excel just fine, but Excel freezes when I try to open the VBE window. I can then CTRL + Shift + ESC and close Excel, which then opens the Personal.xlsb just fine. I can then transfer the modules to a new workbook, and delete my Personal.xlsb, add a new Personal.xlsb, and it all works fine again.
I know that Excel has odd practices for updating the VB Pcode when it compiles, and that can sometimes lead to corrupted code. However this seems to only happen when I'm testing something using a userform. I just wanted to see if anyone had experienced this before / if there was a known issue / or if it's something as simple as poor garbage collecting practices on my part. This doesn't happen often, just about once every two months, but I'm afraid it could carry over to the end user and I'd hate to corrupt their workbook.
Thanks!
I've lately noticed an issue with my Personal.xlsb workbook becoming corrupted when I create a macro that utilizes userforms. I noticed this tends to happen when I'm testing the code, typically after stopping the macro with the blue stop button on the toolbar.
Typically once the data is corrupted, I can open Excel just fine, but Excel freezes when I try to open the VBE window. I can then CTRL + Shift + ESC and close Excel, which then opens the Personal.xlsb just fine. I can then transfer the modules to a new workbook, and delete my Personal.xlsb, add a new Personal.xlsb, and it all works fine again.
I know that Excel has odd practices for updating the VB Pcode when it compiles, and that can sometimes lead to corrupted code. However this seems to only happen when I'm testing something using a userform. I just wanted to see if anyone had experienced this before / if there was a known issue / or if it's something as simple as poor garbage collecting practices on my part. This doesn't happen often, just about once every two months, but I'm afraid it could carry over to the end user and I'd hate to corrupt their workbook.
Thanks!
Last edited:
