If I comment this line out, the rest of the macro runs okay (aside from the glitch of the missing data from the container. Or possibly the temporary string used in the sub-routine is the nominal culprit? Ie, it might be using a similarly named variable from another sub-routine or something wacky. Bread and butter collection use.Īnother possible suspect might be variable scope(?). In particular, it's inserting the 2nd element into the collection. So, while that may be the point of the error, I suspect it has to do with memory of the collection - eg, perhaps it's doing a realloc behind the scenes during this particular insert. (And haven't modified it from the working PC version). Nothing fancy and doing it a zillion other places as well without a problem. The error is happening when adding an element to a collection. Latest office update installed too (14.3 I believe it was)

I'm encountering the ubiquitous EXC_BAD_ACCESS error in Microsoft Office for Mac 2011 on OSX 10.7 (Lion).