MICROSOFT OFFICE 2011 MAC MAVERICKS HOW TO

In the Sub, the variant array was then iterated using a 'For Each' loop (which crashed) For outerLoopIndex=0 To 100Д®xit For ' skip any others since found a site of interest The following is somewhat speculative on what was happening.Д®arlier a variant array was created, populated, and passed to a subroutine. Through some 'printf' debuggging, tracked down the issue. (Experienced programmer, just unfamiliar with OSX. How might I utilize the core dump on the exception to trace the problem? Perhaps excel has a memory limit cap for macros?

Is the memory page 64k on mac like it is on PC?Д¬ould it be physical ram / virtual memory / swapping? (Seems too consistent to be system os related)

MICROSOFT OFFICE 2011 MAC MAVERICKS HOW TO

I'm seeking suggestions on how to go about tracking down the issue. Which can be empty in normal operation so that's handled okay) 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).

Microsoft office 2011 mac mavericks