F
Fritz
Yikes! Can you help me with this puzzle and keep me from going crazy
I have an ongoing problem with Excel in Office 2001 for Mac. I've been using it for two years now (on an iMac DVD). It's just one big document that keeps track of my website traffic and income. The document is now about 20 columns wide and 900 rows long. It includes several simple formulas: adding numbers for all 30 (or 31) days of the month together, dividing the total for the daily average, etc. Each day I open the spreadsheet, add the day's numbers, and close it -- pretty simple stuff
For about a year I've been battling a recurring glitch -- at first it was rare, only occurring maybe once every 30 days. Now it is pretty much every day, and the spreadsheet has become unusable.
Here are the (multiple) symptoms, all of which occur upon opening the saved document
1) Several of the columns are hidden
2) The dates in the date column are replaced with ######
3) New numbers, when entered, are changed to entirely different numbers. For instance, I type in 146,038 and when I hit return, the cell the number changes to 15,239. If I retype the correct number, it changes right back to the bad number.
4) When this happens, the dependent numbers in the rest of the row change from 0 to NUM
5) In money columns, old daily numbers all become "0." However, weirdly, the monthly totals (adding up the 30 individual dates, which read "0") remain with the correct past totals
6) In money columns, new numbers entered are rounded to no decimals. (I enter 29.36, and Excel instantly rounds it to 29.00)
These are the main glitches. Incidentally, if I resize any columns, save and close, when I reopen the file the columns are all back to the default size.
Obviously, it's a huge problem. Before I got around it by shutting down Excel, shutting down the computer, restarting, and then hoping that the glitch would be gone when I opened the document. (Sometimes it was, sometimes it wasn't.) Or I'd just wait a few days, hoping it would fix itself. (Sometimes it did, but now it never does.
Does this sound familiar to anyone? Is there any solution? Is it a combination of problems, or one big foulup
Thanks for any help you can offer, friends
I have an ongoing problem with Excel in Office 2001 for Mac. I've been using it for two years now (on an iMac DVD). It's just one big document that keeps track of my website traffic and income. The document is now about 20 columns wide and 900 rows long. It includes several simple formulas: adding numbers for all 30 (or 31) days of the month together, dividing the total for the daily average, etc. Each day I open the spreadsheet, add the day's numbers, and close it -- pretty simple stuff
For about a year I've been battling a recurring glitch -- at first it was rare, only occurring maybe once every 30 days. Now it is pretty much every day, and the spreadsheet has become unusable.
Here are the (multiple) symptoms, all of which occur upon opening the saved document
1) Several of the columns are hidden
2) The dates in the date column are replaced with ######
3) New numbers, when entered, are changed to entirely different numbers. For instance, I type in 146,038 and when I hit return, the cell the number changes to 15,239. If I retype the correct number, it changes right back to the bad number.
4) When this happens, the dependent numbers in the rest of the row change from 0 to NUM
5) In money columns, old daily numbers all become "0." However, weirdly, the monthly totals (adding up the 30 individual dates, which read "0") remain with the correct past totals
6) In money columns, new numbers entered are rounded to no decimals. (I enter 29.36, and Excel instantly rounds it to 29.00)
These are the main glitches. Incidentally, if I resize any columns, save and close, when I reopen the file the columns are all back to the default size.
Obviously, it's a huge problem. Before I got around it by shutting down Excel, shutting down the computer, restarting, and then hoping that the glitch would be gone when I opened the document. (Sometimes it was, sometimes it wasn't.) Or I'd just wait a few days, hoping it would fix itself. (Sometimes it did, but now it never does.
Does this sound familiar to anyone? Is there any solution? Is it a combination of problems, or one big foulup
Thanks for any help you can offer, friends