Excel VBA Run-time Error '32809' - Trying to Understand it

Question

A colleague at work made some changes to one of our macro workbooks and now on my PC only I receive the dreaded Run-time Error \'32809\' when I attempt to run it. This lates

Answer 1

I've been struggling with this for awhile too. It actually occurred due to some Microsoft Office updates via Windows Update starting in December. It has caused quite a bit of a headache, not to mention hours of lost productivity due to this issue.

One of the updates breaks the forms, and you need to clear the Office cache as stated by UHsoccer

Additionally, another answer thread here: Suddenly several VBA macro errors, mostly 32809 has a link to the MS blog with details.

Another of the updates causes another error where if you create or modify one of these forms (even as simple as saving the form data) it will update the internals of the spreadsheet, which, when given to another person without the updates, will cause the error above.

The solution (if you are working with others on the same spreadsheet)? Sadly, either have everyone you deal with use the office updates, then have them clear the office cache, or revert back to pre Dec '14 updates via a system restore (or by manually removing them).

I know, not much of a solution, right? I'm not happy either.

Just as a back-story, I updated my machine, keeping up with updates, and one of the companies I dealt with did not. I was pulling out my hair just before Christmas trying to figure out the issue, and without any restore points, I finally relented and reformatted.

Now, a month later, the company's IT department updated their workstations. And, without surprise, they began having issues similar to this as well (not to mention when I received their spreadsheets, I had the same issue).

Now, we are all up on the same updates, and everything is well as can be.

Answer 2

In my case, the error occurred executing a macro in: Sheets("own sheet one").Select

copy the sheet into another with other name, ie. "oso", then delete the original sheet and renamed the new one as "own sheet one"

Excel 2013

Answer 3

Ok, this might be weird. Anyway one of my colleagues had this error and we tried the edit VBA compile whatever. But the thing is, just copy the excel file to the desktop. And it worked. The Excel file was originally in a network drive. This worked, this is my answer to this issue.

Answer 4

I did the following and worked like a charm:

1. Install Office 2013 (I haven't tried with 2010 but I think it would work too).
2. Install Office 2013 SP1.
3. Run Windows Updates and install all Office and Windows updates.
4. Reboot computer.
5. Done.

This worked for me in two different computers. I hope this will work in yours too!

Answer 5

In my case following helped:

1. Save file as .xlsx (macro-free) - all macros would be erased while saving;
2. Open source file with macros and copy modules to the .xlsx file;
3. Save file as .xlsm - full recompile performed.

Afterwards everything started working normally. I had file with 200+ sheets and 50+ macros and posting comments in each module didn't help, but this solution worked.

Answer 6

This worked for me using excel 2010 and getting the same error when opening a macro-enabled .xlsm file.

-after dismissing the error dialog, do "save as" tab-delimited .txt file. click OK for

...only active sheet.

...functions not saved.

-then "save as" again, but this time select macro-enabled .xlsm format. (to another file or overwrite original doesn't matter, but save as another feels safer.)

-close out excel.

-open the newly saved .xlsm file. In my cases, the error messages went away and the macros are working.