Welcome to MSDN Blogs Sign in | Join | Help

Microsoft Excel

The team blog for Microsoft Excel and Excel Services.
Some other numbers ...

As part of the Excel team’s work to increase the number of rows and columns in Excel 12, we also increased a number of the other “limits” in the product.  This work falls into a two categories.

First, we increased a number of limits to support our “big grid” work.  These are limits that we increased to make sure that all of Excel’s features could scale to handle more rows and columns.  A lot of folks have already asked about these sorts of limits in comments to my first post, in emails, and in comments on other blogs and websites.  For example, we increased the number of rows allowed in a PivotTable from 64k to 1 million (2^20 to be precise), we increased the amount of memory that Excel can use from 1GB to the maximum allowed by Windows, and we completely eliminated the limit on the number of rows of a column or columns that can be referred to in an array formula.

Second, we took the opportunity to increase a number of other limits that our customers had asked us to increase over the years.  For example, we increased the number of colours allowed in a single workbook from 56 (indexed colour) to 4.3 billion (32-bit colour), and we increased the number of characters that can be stored and displayed in a cell formatted as Text from 255 to 32k.  We increased the number of levels of sorting possible on a range, and the number of conditional formats possible on a cell.  Some of these limits – like the number of levels of sorting possible on a range – obviously require UI changes; I will discuss those in later posts when I cover the other work we have done in those areas.

Here is a list of all of the major changes we made to Excel 12 in the area of limits.

The total number of available columns in Excel
Old Limit: 256  (2^8)
New Limit: 16k  (2^14)

The total number of available rows in Excel
Old Limit: 64k  (2^16)
New Limit: 1M  (2^20)

Total amount of PC memory that Excel can use
Old Limit: 1GB
New Limit: Maximum allowed by Windows

Number of unique colours allowed a single workbook
Old Limit: 56 (indexed colour)
New Limit: 4.3 billion (32-bit colour)

Number of conditional format conditions on a cell
Old Limit: 3 conditions
New Limit: Limited by available memory

Number of levels of sorting on a range or table
Old Limit: 3
New Limit: 64

Number of items shown in the Auto-Filter dropdown
Old Limit: 1,000
New Limit: 10,000

The total number of characters that can display in a cell
Old Limit: 1k (when the text is formatted)
New Limit: 32k or as many as will fit in the cell (regardless of formatting)

The number of characters per cell that Excel can print
Old Limit: 1k
New Limit: 32k

The total number of unique cell styles in a workbook (combinations of all cell formatting)
Old Limit: 4000
New Limit: 64k

The maximum length of formulas (in characters)
Old Limit: 1k characters
New Limit: 8k characters

The number of levels of nesting that Excel allows in formulas
Old Limit: 7
New Limit: 64

Maximum number of arguments to a function
Old Limit: 30
New Limit: 255

Maximum number of items found by “Find All”
Old Limit: ~64k (65472)
New Limit: ~2 Billion

Number of rows allowed in a Pivot Table
Old Limit: 64k
New Limit: 1M

Number of columns allowed in a Pivot Table
Old Limit: 255
New Limit: 16k

Maximum number of unique items within a single Pivot Field
Old Limit: 32k
New Limit: 1M

Length of the MDX name for a Pivot Table item; also the string length for a relational Pivot Table
Old Limit: 255 characters
New Limit: 32k

The length at which fields’ labels are truncated when added to PivotTable; this also includes caption length limitations
Old Limit: 255
New Limit: 32k

The number of fields (as seen in the field list) that a single PivotTable can have
Old Limit: 255
New Limit: 16k

The number of cells that may depend on a single area before Excel must do full calculations instead of partial calculations (because it can no longer track the dependencies required to do partial calculations)
Old Limit: 8k
New Limit: Limited by available memory

The number of different areas in a sheet that may have dependencies before Excel must do full calculations instead of partial calculations (because it can no longer track the dependencies required to do partial calculations)
Old Limit: 64k
New Limit: Limited by available memory

The number of array formulas in a worksheet that can refer to another (given) worksheet
Old Limit: 65k
New Limit: Limited by available memory

The number of categories that custom functions can be bucketed into
Old Limit: 32
New Limit: 255

The number of characters that may be updated in a non-resident external workbook reference
Old Limit: 255
New Limit: 32k

Number of rows of a column or columns that can be referred to in an array formula
Old Limit: 65,335
New Limit: Limitation removed (full-column references allowed)

The number of characters that can be stored and displayed in a cell formatted as Text
Old Limit: 255
New Limit: 32k

For those of you that read this far, thanks.  Next post I will step back a bit and review all the areas where we have made feature investments in Excel 12.  It is a pretty big list, and I am excited to share it with you.

PS Updated to fix a typo

Posted: Monday, September 26, 2005 10:17 PM by David Gainer

Comments

anon said:


"we increased the number of characters that can be stored and displayed in a cell formatted as Text from 255 to 32k"

Hmm? Zero improvement here, that's available since Excel 97. I installed good ol' Excel 97 the other day and this feature title appears on one of the install screens while installing.

What could possibly be fixed however, is that there were clipboard and round-tripping problems with the COM OM when using cells with more than 255 bytes under certain circumstances. Since Excel 97.
# September 27, 2005 3:15 AM

Sam said:

Hi David
How about
1) Validation - Allowing list types to be referenced from other sheets/workbooks
- Workaround - Defined names
2) Circle Invalid Data - Limited to 256 Red circles (I think)
3) Copy - Paste on Validated Cells removes validation without warning,same for conditional fromating
4)Allow Macors to work in the "Cell Edit Mode"
5)Improving the Interface for Advanced Filter
6) Improving the Syntax of all Database functions...DSUM,Dcount etc

Sam
# September 27, 2005 3:36 AM

Boris said:

How about improving the way INDIRECT works?
I know the official line is that Excel is not a Lotus 123 clone but their version (@@) has considerably more flexibility when creating variable links to other files.
# September 27, 2005 4:00 AM

Boris said:

Two things about this one:

Number of levels of sorting on a range or table
Old Limit: 3
Old Limit: 64

1) I think you meant that the NEW limit is 64
2) You know that Lotus 123 has had an unlimited restriction on this since its original DOS 3D version?

Pip pip

# September 27, 2005 4:04 AM

Frank said:

So how will the columns be numbered? 3 characters?
# September 27, 2005 4:16 AM

Sam said:

Hi David.
Please do not change the interface... the worst nigthmare I can imagine is to start finding all the buttons again!!

Dont try and improve something thats working fine already
Sam
# September 27, 2005 4:27 AM

Boris (once more) said:

DSUM function, and all the other D functions.

Allow SQL syntax as the argument rather than having to set up a criteria range ... a bit like the wat 123 has been doing it for years :-)
# September 27, 2005 5:09 AM

Nigel Harper said:

David,

Well done to you and your team. This is a quantum leap forward in many areas, and is certainly more than I expect many people believed would be delivered. I can't wait to get my teeth into it
Could we hear a little more about the Calculation side of things (Dependency Tree, Calculation Algorithms) given that it already can be slow to calculate some array formulas over a couple of thousand rows let alone trying it over a couple of hundred-thousand. In other words how are you catering for this increase in worksheet size in the calculation engine?
Also, could we hear a little more about the Object Model (will we be seeing a full diagram anytime soon?) and VBA side too? One of my personal bug-bears is trying to place long array-formulas in cells via VBA and being limited to the 255 character length string for the formula when being entered in by code this way.
# September 27, 2005 7:14 AM

Jim Rech said:

Anon:

>>"we increased the number of characters that can be stored and displayed in a cell formatted as Text from 255 to 32k"

>>Hmm? Zero improvement here,

1. Enter =REPT("a",256) in A1
2. Now change A1's number format to Text.
# September 27, 2005 10:22 AM

Adam Gentry said:

I work for a large bank and we currently are pushing the boundaries of what your product can support. One of those boundaries we encountered is in defining a range with a large quantity of non-contigous cells. If you define a named range and the length of the string of cells locations (including page names) exceeds 255 characters an error is thrown up. We currently have a CDCR with your organization and if this can not be solved in the current version, I would highly recommend removing this limitation in the next.

Reg,
Adam
# September 27, 2005 10:27 AM

Kaleb said:

Will these changes mean changes to the BIFF format, or are the new limits supported only with the new XML-based format?
# September 27, 2005 11:47 AM

John Greenan said:

This is all very good sounding stuff. Could you please take a moment to describe any changes you are making to the RTD components of Excel?

While RTD is much better than the very clunky DDE server, it's still lacking in features and in granularity of control.

Thanks in advance,

John
# September 27, 2005 11:50 AM

simon murphy said:

David
Thanks for the info - very useful.
Q: Is VSTA going to be there alongside VBA??
cheers
Simon
# September 27, 2005 1:30 PM

anon said:


Outline levels? (currently limit is 8)
# September 27, 2005 2:39 PM

simon murphy said:

Message for Adam Gentry
Bob Umlas has some workarounds for this in his new book - its not Excel its magic.
1. temporarily rename sheet to 'a' whilst defining range, rename after
2. create 'sub' names and union them together
3. Select and use the name box - limit here 224 or so non contigous areas
cheers
Simon
# September 27, 2005 5:15 PM

Susan said:

I second increasing the number of outline levels.
# September 27, 2005 10:28 PM

Maurice said:

Absolutely incredible!
# September 28, 2005 12:01 AM

Chartman of the Bored said:

"Next post I will step back a bit and review all the areas where we have made feature investments in Excel 12."

I'm keeping my fingers crossed that one of these includes a "Median" option in pivot tables... Seems like a no-brainer... More support/options for calculated fields would help too! End of rant.

Thanks for the updates!
# September 28, 2005 2:07 AM

David Gainer said:

Again, thanks very much for your interest and questions and comments.

Sam, Boris, Adam, anon, Susan – The list of limits above that we worked on this time is pretty much complete; we didn’t make changes in Excel 12 to the further areas you asked about.

Frank – The new columns will be characters continuing from where we leave off today – column 257 will start at IV and columns will continue up to XFD.

Nigel – I will write an article in the future about our calculation changes, so bear with me – we have a lot to talk about this release! I will also add VBA OM additions to my list of topics.

Jim – Thanks for the clarification.

Adam – See Simon’s comments below, and thanks for the feedback.

Kaleb – The answer is a bit of both, and compatibility will be another place where I will write a few posts at some point in the future. Some of the limits – like rows and columns – will only be available using Excel 12 files. Other limits – like more colours – can be successfully round-tripped through BIFF8 files (Excel 97 – 2003 format), although you won’t see the colours in earlier versions of Excel.

John – We have not made any changes to RTD in this version.

Simon – For the core Office apps, VBE remains the integrated development environment.
# September 28, 2005 3:17 AM

Rob van Gelder said:

David,

Thank you for taking the time to answer questions.

I have some solutions where I use QueryTables Parameters.
Querytables come in a few flavours. I use ODBC Querytables mostly. I want to use OLEDB querytables but Parameters dont work for them. Only ODBC querytables support parameters.

Could you please comment on whether OLEDB querytables will support parameters?
# September 28, 2005 4:25 AM

David Gainer said:

Hi Rob - we have not made any changes to querytables and paramaters.
# September 28, 2005 11:50 AM

calvin said:

What about the number of sheets?
# September 29, 2005 1:02 AM

Harlan Grove said:

Jim Rech...
>Anon:
>
>>>"we increased the number of characters that >can be stored and displayed in a cell >formatted as Text from 255 to 32k"
>
>>>Hmm? Zero improvement here,
>
>1. Enter =REPT("a",256) in A1
>2. Now change A1's number format to Text.

Alternatively, with A1 not initially formatted as Text enter

=REPT(REPT("a",255),128)

then change A1's number format to Text.

If anything the functionality you mention would seem to be a bug in the interaction between REPT called with a 2nd argument >= 256 and the Text number format. Yes, it is nice that Microsoft is fixing bugs, but I'll wait to see how XL12 handles MOD(2^30,3) before deciding whether they've been thorough or not.
# September 30, 2005 4:38 PM

Joseph said:

-A suggestion for a new feature

It would be nice to see Application settings to have a worksheet specific option (Example: Calculation settings). This would be nice to have so the settings won't affect any other open workbook and/or any other worksheet.
# October 1, 2005 11:28 AM

Andrew said:

>If anything the functionality you mention would seem to be a bug in the interaction between REPT called with a 2nd argument >= 256 and the Text number format.

No, it's not. If you type 256 a's into a cell, and format it as text, you'll see the same behavior as if you used REPT and formatted it as text.
# October 3, 2005 1:42 PM

Harlan Grove said:

Andrew...
||If anything the functionality you mention
||would seem to be a bug in the interaction
||between REPT called with a 2nd argument
||>= 256 and the Text number format.
|
|No, it's not. If you type 256 a's into a
|cell, and format it as text, you'll see the
|same behavior as if you used REPT and
|formatted it as text.

There's a bug somewhere. I'm willing to grant it may not be in the REPT function. However, in Excel 2002 (at least), if you open a new workbook with default number format other than Text, enter the formula

=REPT(REPT("a",255),128)

then format the cell as Text, Excel continues to display a long string of a's. Not all 32640, but much more than the width of the cell. Why does Excel Text number format choke on a formula-generated string of 256 chars but not on a formula-generated string of over 32K chars? How do you define 'bug'? I suppose you could hide behind programming terminology and call this an instance of nonorthogonality rather than a bug.
# October 3, 2005 6:40 PM

Jan Karel Pieterse said:

Adam:

About the long defined names:

Download my name manager utility from

www.jkp-ads.com/OfficeMarketPlaceNM-EN.htm

It allows you to edit names with mulitple areas without being bothered by the 244 character limit.
# October 4, 2005 5:48 AM

Scott said:

"
The total number of available columns in Excel
Old Limit: 256 (2^8)
New Limit: 16k (2^14)

The total number of available rows in Excel
Old Limit: 64k (2^16)
New Limit: 1M (2^20)
"

It's about time. Now please release the software. We needed this years ago, not years from now.
# October 4, 2005 8:40 AM

David Gainer said:

Greetings,

Calvin – We have not changed any limits around the number of sheets.

Harlan – As you have identified, the problem with characters formatted as text only appeared in cells containing between 255 and 1024 characters (text displays “####” instead of the characters).

Joseph – We have done some work in application settings to make it much clearer which settings relate to a specific workbook. Watch Jensen’s UEX blog for details, and I may write something too at a later point.

Scott – Glad you like the feature. We are doing our best!
# October 5, 2005 1:22 AM

Rob van Gelder said:

I wondered about the column/row limits. Why were there limits at all?

My guess is that in "unlimited mode", any series of characters followed by any series of numbers would be treated as a cell reference.

eg. vangelder1 would be a valid cell reference.

Is this the reason to limit the number of cells on a worksheet or was there some other reason? I'm interested to know.

Cheers,
Rob
# October 9, 2005 3:36 PM

Peter Quarrell said:

I really am pleased that the limit of "approximately 4000" on the number of different cell formats (inadequately discussed in http://support.microsoft.com/default.aspx?scid=kb;%5BLN%5D;213904) is to be increased to 64K.

BTW you refer to this limit as being on "the total number of unique cell styles". This term is also used in the KB paper listed above, and by several of those who have posted comments about the problem in various places. The reference to "styles" actually confuses people, and takes attention away from the fact that this limit is on something (format combinations) when most people don't know of its existence. You will find, if you do a Google search, that some people think the problem can be solved by deleting unused custom number formats, but they don't make the combinations list hit its limit.

I'm pleased the limit is being increased even though this means there will be an end to a steady small income I have been making for a few years from sales of my utility QAid. Although QAid offers quite a range of useful analyses to improve the efficiency of large Excel workbooks, most of the sales go to people who have run into the "approximately 4000" limit (actually anything from 2300 to 4482 in my experience) and discovered that it makes the workbook _completely_ unmanageable. When you open the workbook, up comes the error message; whatever you do to it then, up comes the error message again. (But see my web site for advice on how to get it working, and thus repairable, again).

Since creating my website to publicise QAid some years ago, I have been contacted on average once every 14 days by someone interested in acquiring a QAid licence. QAid works by identifying and counting occurrences of each of the format combinations used, thus producing a shortlist of those which are used once only and can therefore reduce the problem by being changed to a less unique format. In the last 18 months QAid has also provided shortlists of the combinations most similar to the one you want to eliminate, thus almost automating the mending process (while leaving to the developer the necessary choice of which feature(s) of the combination to sacrifice).

So hopefully my sales of QAid will begin to dry up once Excel 12 is on the market -- indeed, I will be duty bound to add a note to my web site advising interested potential customers to switch to Excel 12 to sort out their problem. It seems sad, really; I've had emails from all over the world, with recent sales including the US Department of Treasury, a Hollywood studio, a major oil company, local governments in 3 continents, a New Zealand sawmill, and an Australian bank. Often we have corresponded at some length as new vagaries in Microsoft's offering have become apparent.

Two main questions:

(a) does the increase to 64K mean that workbooks that hit the new limit will give some warning and not become unmanageable just as their victims discover the problem? If users could try to deal with the limit without having to worry about whether their workbook can ever be made useable, they might not feel as bad about Microsoft as most of them do (there is a universal feeling among them that this aspect of Excel must have been developed by a Seattle high school student on work experience during the summer vacation, who was inadequately supervised because the managers who should have done so were on vacation themselves -- and that customer complaints have not got through often enough for anyone to consider doing the repair work that has been needed since day 1).

(b) is there any chance that Microsoft might give users some VBA access to the parts of the Excel Object Model that deal with these format combinations? There must be a hidden list of all the different combinations, with all the relevant format property values for each one, and a pointer system in one direction at least (from cell to list) if not in both directions. QAid generates such a list (and takes ages, since it has to evaluate 40 different format aspects for every single cell _and_ merged area in the workbook's full UsedRange). Give us read-only access to the list and the task becomes much less.

The Object Model's list seems not to be particularly often subjected to housekeeping (just as deleting hunks of VBA leaves unused gaps in a workbook, which can only be closed up by exporting all the forms and VBA modules, saving the workbook, and then reimporting them). When a workbook is close to the ~4000 limit (a state identified by formatting a cell with a previously unused font or colour, and watching it crash), the margin for new formats can best be increased by _both_ saving the workbook _and_ exiting Excel completely. It looks as though only closing Excel actually tidies up that aspect fully. Not very easy to prove that point, but I've given that advice frequently, and many people have found it helpful.
# October 11, 2005 5:51 AM

David Gainer said:

Peter – Thanks for your comments. We believe that increasing the limit roughly 16 fold will dramatically reduce the number of users that ever hit this limit. Secondly, in a world of more structured formatting with improved cell styles, table styles, and themes (which I will cover in later posts), we believe there will be less need to create one-off formats, so it is possible that the average number of unique formats an Excel 12 workbook will be fewer than an Excel 11 workbook. Finally, both cell and table styles have their own 64k limits separate from each other and the “unique cell styles” limit in question. The result is that cell styles and table styles take zero slots from the custom format limit.
# October 19, 2005 12:46 AM

Microsoft Excel 12 said:

The Final LookFor most of the history of this blog, I have been showing you screenshots produced using...
# March 9, 2006 4:14 PM

Microsoft Excel 2007 (nee Excel 12) said:

One of the themes we focused on with Office 2007 was “great looking documents”.  For the next half-dozen...
# March 13, 2006 2:27 PM

Microsoft Excel 2007 (nee Excel 12) said:

To this point in the blog, I haven't talked too much about the file formats that Excel 2007 uses, since...
# July 20, 2006 5:39 PM

Alexander Holy's Weblog said:

The new Excel File Formats. Like all "new" file formats coming along Vista and Office 2007, these...
# August 23, 2006 7:21 AM

excel text limit said:

# June 20, 2008 8:27 PM

65536 | keyongtech said:

# January 21, 2009 11:41 PM
New Comments to this post are disabled
Page view tracker