Note that there are some explanatory texts on larger screens.

plurals
  1. POEXC_BAD_ACCESS "Office for Mac 2011" Excel macros MicrosoftOleautomation debug cause
    primarykey
    data
    text
    <p>I'm encountering the ubiquitous EXC_BAD_ACCESS error in Microsoft Office for Mac 2011 on OSX 10.7 (Lion). Latest office update installed too (14.3 I believe it was)</p> <p>I'm running a (rather large) macro ... Porting it from PC Office.</p> <p>The error is happening when adding an element to a collection. Nothing fancy and doing it a zillion other places as well without a problem. (And haven't modified it from the working PC version).</p> <p>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.</p> <p>In particular, it's inserting the 2nd element into the collection. No user defined type. Nothing special. Adding a string element. Data being inserted is kosher. The key ID is unique. Bread and butter collection use.</p> <p>Another possible suspect might be variable scope(???) ... Ie, it might be using a similarly named variable from another sub-routine or something wacky.</p> <p>Or possibly the temporary string used in the sub-routine is the nominal culprit?</p> <p>If I comment this line out, the rest of the macro runs okay (aside from the glitch of the missing data from the container ... Which can be empty in normal operation so that's handled okay)</p> <p>I'm seeking suggestions on how to go about tracking down the issue. And tips towards resolving it.</p> <p>Is the memory page 64k on mac like it is on PC?</p> <p>Could it be physical ram / virtual memory / swapping? (Seems too consistent to be system os related)</p> <p>Perhaps excel has a memory limit cap for macros?</p> <p>How might I utilize the core dump on the exception to trace the problem?</p> <p>(Experienced programmer, just unfamiliar with OSX ... And missing all my PC dev tools <em>sigh</em>)</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload