Re: multiple bugs in Excel 2008 (12.0.1)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Chris,

Thanks for the detailed reports. The workbooks and examples were extremely
helpful.

I'm going to ask someone to investigate the printing problem and see if they
can duplicate it since on cursory examination I don't see the same result
that you do. My available configurations are limited where I'm at though so
I'm sure we'll spot the problem with the right hardware. Can you tell me
what printer and driver you're using? That will help our engineer select
hardware to test on that is similar to what you're using.

Good catch on the protected workbook becoming unprotected when copying it.
That's actually my area of responsibility and I must have flat-out missed
that case. I'm sorry. We're tracking that in our internal bug database now.

The next bug is a little trickier in the sense that data validation is
involved but not the only part that's important. There are a lot of features
being exercised on that *** and a combination of them are causing the
problem. If you create a work*** with just a validated list, select the
cell that's validated and delete the ***, there is no crash. The workbook
you sent will be helpful locating the eventual problem here and we're
tracking it now in our internal bug database.

It was late last night that I was working on the final bug and I have to
admit that at first I saw it on 12.0.1 and then into the wee hours of the
morning I wasn't seeing it. I'll ask the sort experts to investigate it
though because my knowledge is limited there. For a time during the project
prior to release we weren't populating the column name at all in the sort
dialog, but there are no other current reports of it losing it's "memory".

Thanks again for taking the time to report the problems you're having and
for using the level of detail that you provided. The research takes effort
and I appreciate the amount you invested.

Todd Aton
Macintosh Business Unit
Microsoft Corporation

Microsoft makes no warranties, express, implied or statutory, as to the
information in this post.




On 3/17/08 10:02 AM, in article 2008031713021916807-likeireadthis@gmailcom,
"Chris Bailey" <likeireadthis@xxxxxxxxx> wrote:

I've discovered a couple of bugs in Excel 2008 (12.0.1, running on Mac
OS X 10.5.2, 3G RAM on MacBook Pro Core 2 Duo 2.33GHz). I'm not sure if
there's a better way to report them to Microsoft, so I'm posting them
here in the hopes they get looked at.

1. Sometimes cells print blank
This seems to happen predominantly with cells that have long strings of
text (200 chars or more). I've uploaded an example Excel file and PDF
printout of what comes out. I've found that if I reduce the number of
characters in the cell, it prints, but the number of characters varies
from session to session. For instance, cell D2 in the example *** has
649 characters. When I was testing earlier today, I had to reduce it to
438 characters to get it to print. Just now I tried again and got a
printing cell when it was trimmed to 575 characters. This problem
affects both printouts to a printer and printing to Adobe PDF format
(or using the Mac's built-in Save to PDF feature). I've also just tried
using Excel 2008's ability to save in PDF format, and this cell comes
out blank as well. I can say for sure this problem did not occur with
Excel 2004, as I used to have extremely long wrapped text cells used in
my invoice and never got a blank cell like I get frequently now.

http://www.fortbailey.com/excel2008/cellproblem.xlsx
http://www.fortbailey.com/excel2008/cellproblem.pdf

2. Copying a protected work*** results in an unprotected work***.
I use Excel to do my time*** at work every day. At the end of the
day, I make a copy of the current work*** to the end of the workbook,
and keep only the last three days. Since my master time*** page has
several formulas and validation look-ups, I want to make sure I don't
accidentally delete any of them, so the *** is protected. However,
I'm finding the copies of the protected sheets I'm making are coming
out unprotected. This is a change in behavior from Excel 2004. In the
example listed below, take the "time***" tab (which is protected) and
make a copy of it; it will be an unprotected duplicate.

http://www.fortbailey.com/excel2008/sheetproblem.xlsx

3. Attempting to delete a work*** that has an in-cell dropdown
selected causes Excel 2008 to quit
This problem uses the same example file as problem #2. Columns F, G, I,
K and M all contain validation formats with in-cell dropdowns. For
instance, clicking in column F brings up a drop-down menu of jobs
listed in column Q so you don't have to type job numbers over and over
again. Click in any of these cells (F4, for example) and then attempt
to delete the active work***. Excel will quit.

4. Sort criteria not retained
Another example of how behavior in Excel 2008 differs from 2004 is
found in sort memory. The example file listed below is a list of bills
and when they were paid last (although I've obviously genericized it up
for privacy reasons). When I update this file, I always sort it by
column C (the "last paid" date). Using Excel 2004, every time I opened
this file, selected my data and went to sort it, I found it would
automatically remember which column I had selected last. Now each and
every time, it reverts to column A.

http://www.fortbailey.com/excel2008/sortproblem.xlsx



.

Quantcast