But if you work with primarily Windows users who use Office, it's tough to beat the automatic compatibility of using the same programs. Certainly many Mac users will look first at Apple's iWork for a productivity suite, and it is a great office suite in its own right. Once we dug deep into the feature set of Office 2011 for Mac, we saw there were several enhancements that made the whole suite better, and some of the niftier tweaks are even Mac-exclusive. Not only has it nearly reached feature parity (and cross compatibility) with the Mac counterparts to Word, Excel, and PowerPoint, but it has finally added Outlook, the e-mail and scheduling client Mac business fans have been clamoring for for years. Though the latest package is still not on par with the Windows version (you get only the four main programs-a big difference when you consider the Windows version has 10), Microsoft made a big leap with this latest version for the Mac in several other ways.
#Office 2011 for mac for mac
Mac Excel seems to be more sensitive to such things.Microsoft Office for Mac 2011 offers a solid update to the Word, Excel, PowerPoint, and the other members of the productivity suite. Perhaps this will help others running into similar issues. The "fix" was to explicitly declare as Variant: Dim currName As Variant However, data becomes corrupted such that, on the second pass through the outer loop, the EXC_BAD_ACCESS crash occurred. It worked correctly on the first pass of the outer loop. 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)
#Office 2011 for mac 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.
#Office 2011 for mac Pc
(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).
0 kommentar(er)
