Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
All day every day at work I deal with a series of spreadsheets with somewhere between 30,000 - 50,000 rows and 50-60 columns so in the region of 1.5 million - 3 million cells. There can be up to 12 people working on the document at once.

Have you considered using an actual database for this or are you just masochistic by nature? :)
 
I think it is easy for those of us who no longer use Windows to forget that Office is an over-bloated suite of programs, regardless of the platform you decide to use to run it. So, most of us will stick with iWork. But really, if you think about it for a minute, does any part of this announcement surprise you at all??:confused:
 
Although this won't even really affect me- this is on track to be the worst MS Office release ever. No OneNote, 32 but only, icons that look like they were made in KidPix...
 
All day every day at work I deal with a series of spreadsheets with somewhere between 30,000 - 50,000 rows and 50-60 columns so in the region of 1.5 million - 3 million cells. There can be up to 12 people working on the document at once.
pun1.jpg


The bus is Excel.
 
I was formatting a 50 page document of 2008 Office for Mac and it's almost impossible to work. It lags while scrolling (badly) and eats 400 MB RAM (yep) only 3 charts and everything else text only. Finished on Pages in no time.

If you cant spare 400mb's of RAM for the current active application you are running, then you need to look at upgrading. 400mb RAM usage isnt a lot anymore, and hasn't been for a while.

I'll admit, I find Word a bit laggy, but you do have a choice: put up with it, or use iWork and stop bitching.

Sorry to put it so bluntly, but this is NOT a major issue, its a smart move from Microsoft. Work on getting the compatibility right before adding in something that will only have an impact on about 1% of its users.
 
The bus is Excel.

Have you considered using an actual database for this or are you just masochistic by nature? :)

Yes:

xUKHCx said:
Or you are limited to IT policies and the training of long standing employees.


When people you deal with try printing a small dataset (12,000 x 20) so that they can do work on paper then update it back onto that dataset you so realise that the very word database scares a lot of people. They can just about handle excel so anything more will cause more pain then benefit, not to mention the fact that IT won't allow or provide for training/database programs apart from those who absolutely need it. Excel can be configured to be a reasonably ok database and just about everyone knows how to at least do something with excel and just about every office has excel.
 
Can't wait to watch the chorus of "OMG this is 2010... why can't I type my essay in 64-bit????" make themselves look foolish.

+1 Insightful.

I deal with some insanely large Excel spreadsheets. And by "insanely large", I mean 200-300 MB. *WELL* short of the 4 GB limit of a 32-bit process.

Likewise, I occasionally deal with Word documents and PowerPoint documents that have extremely-high-resolution photos in them (I leave them in max res, and compress before distribution,) and even those rarely get over 1 GB. Again, still very short of the 4 GB limit of a 32-bit process.

There is NO compelling reason for Microsoft Office for Mac to be a 64-bit application. Now, certain instructions do execute faster on 64-bit Intel than 32-bit Intel; but even those only add up to a 10% speed boost, max, when using solely those instructions. Excel *MAY* be able to benefit some from those; but 10% isn't exactly a deal-killer. Even my largest spreadsheets only take 10-15 seconds to recalculate on a first-generation, 32-bit-only Core Duo MacBook Pro. On my Octo-core 3.2 GHz rig, it's essentially instantaneous.
 
On the multiuser support in Excel, Microsoft notes this:

"Tip Excel does not offer the same level of multiuser support as does Microsoft Access. For example, Access supports user-level security, but Excel does not. If you have more complex needs for data entry, protection, or reporting than Excel can manage, consider using Access. For information about sharing data between Excel and Access, see "Sharing Information with Microsoft Access 97" in Chapter 27, "Sharing Information with Microsoft Office Applications."

On the multiuser support in Access, I note this: If you care about your data, don't do it. Use an actual database instead.
 
When people you deal with try printing a small dataset (12,000 x 20) so that they can do work on paper then update it back onto that dataset you so realise that the very word database scares a lot of people. They can just about handle excel so anything more will cause more pain then benefit, not to mention the fact that IT won't allow or provide for training/database programs apart from those who absolutely need it. Excel can be configured to be a reasonably ok database and just about everyone knows how to at least do something with excel and just about every office has excel.
I use Excel for my budget.

Everyone else seems to use Excel for page layout. I've seen far too many calendars and newsletters done in Excel. :rolleyes:
 
+1 Insightful.

I deal with some insanely large Excel spreadsheets. And by "insanely large", I mean 200-300 MB. *WELL* short of the 4 GB limit of a 32-bit process.

Just out of curiosity: why? A 200 MB Excel spreadsheet would scare the living daylights out of me.
 
If they get it together and make Entourage into Outlook and make it as good as Windows Outlook is, then they have a sale. 64bit or no.

Having said that I do hope they take the time to get rid of some of the bloat.
 
When people you deal with try printing a small dataset (12,000 x 20) so that they can do work on paper then update it back onto that dataset you so realise that the very word database scares a lot of people. They can just about handle excel so anything more will cause more pain then benefit, not to mention the fact that IT won't allow or provide for training/database programs apart from those who absolutely need it. Excel can be configured to be a reasonably ok database and just about everyone knows how to at least do something with excel and just about every office has excel.

Fair enough. On the other hand, if data integrity was a concern, I wouldn't want to rely on Excel.
 
First of all: 64-bit is useless for Office. So no biggie.

But on second thought: it's pretty pathetic after eight years of OSX, MS still can't make the jump to 64 bit. I mean come on! It's been soooooo many years already! Put a little effort in it. Stuff like this isn't hard.

I am left wondering if Office 2011 is 100% Cocoa, but from the post I reckon it's still a Carbon monstrosity with all kinds of UI approximations. For me, that means no sale still.

Horse crap. Large Data sets alone that can be drawn from Oracle or other RDBMS sources and one wanting to do say Fast Fourier Transforms for Engineering data acquisition is just one of thousands of reasons to have 64 bit clean apps.
 
Hey, at least the guys at Redmond are developing (developing! developing! :D) software for the Mac, unlike the good folks at Cupertino.

The most important software announcement during WWDC for the Mac and it has to come from MS. This are strange times indeed.
 
Hey, at least the guys at Redmond are developing (developing! developing! :D) software for the Mac, unlike the good folks at Cupertino.

The most important software announcement during WWDC for the Mac and it has to come from MS. This are strange times indeed.

Don't forget FaceTime ;)
 
I know I'd rather have Windows Office files open and work properly using Mac Office any day of the week. Gods know M$ can't keep these two development paths together to save their lives - but nor do they care to.

What this tells me more is how much of an ugly stepchild the Mac Business Unit really is within Microsoft. They keep going back to the "lack of resources" excuse for every iteration of Office: Office 2008 doesn't do Macros, it's a "lack of resources," Office 2011 is 32-bit only, it's a "lack of resources."

Like M$ has any problems with resources, this is and has always been about priorities.
 
Horse crap. Large Data sets alone that can be drawn from Oracle or other RDBMS sources and one wanting to do say Fast Fourier Transforms for Engineering data acquisition is just one of thousands of reasons to have 64 bit clean apps.

You don't actually need a 64-bit app to do 64-bit calculations. "double" precision calculations have been around for some time, explained here: http://en.wikipedia.org/wiki/Double_precision_floating-point_format

I believe the internal representation used by 32-bit Excel for numeric types is a 64-bit value.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.