I agree that the new format is much more difficult to work with.
![BangHead :BangHead:](//d1o9fadw0wez7f.cloudfront.net/Smileys/Lots_O_Smileys/BangHead.gif)
I think they were trying to merge the menu with the toolbar to make the menu system a little more user friendly, but I think it actually backfired on them. The old toolbars allowed the user to have all of their common buttons showing at the same time; before if I wanted to make a heading by bolding the text and indenting it, I could do so with a couple of clicks on the toolbars. But now, I have to click the Home ribbon-tab (if it's not already there), click on the Bold text, click on the Page Format ribbon, and finally click on the Indent button. Newer versions are supposed to increase productivity, but it seems like the new version actually detract from that. I remember the first time I used it, it took me over an hour to find the "Print..." function... I didn't realize the Microsoft symbol was actually another tab.
And don't get me started on Excel... being a programmer, I have to write a bunch of programs that have to read data out of an Excel spreadsheet. For example I may write a program that reads data for a user-entered store, and my program will create a config. sheet for that particular store. However there has never been a good way to read data out of a spreadsheet if a column of data has a mix of both numbers and text data. For example the serial number of a computer may be comprised of 7 alpha-numeric characters. This means that one system could have all numbers while a second has a mix of letters and numbers. When Excel comes to these "mixed type" columns, it determines the data-type by a majority of the type based off of the first 8 rows (yeah, I know... 8 only?!) So if your rows are sorted by Serial Number and you have several hundred rows of data, the first 8 rows will all be numeric so Excel will report all data in that column as numeric -- and any text-data in that column will be sent back as NULL (or no data). To make matters worse, numeric data longer than 11 digits are converted into scientific notation (so you're SOL if you are putting in a long S/N or a 12-digit MAC Address without any octet separators). And finally numbers only retain up to 15 significant digits; thus a 16-digit number would have the first 15 digits followed by a zero. These number issues also occur if you try to open a CSV file directly by double-clicking it instead of importing the text-data and ensuring that you assign each row as text data instead of numeric data. With all of these issues (that could easily be resolved if Excel reported every unknown data-type as a variable-length string) it boggles the mind that MS would spend time addressing formatting "issues" (which as mentioned above created more problems than it solved) instead of fixing an issue that MANY programmers and data-entry personnel have repeatedly griped about.
![bs :bs:](//d1o9fadw0wez7f.cloudfront.net/Smileys/Lots_O_Smileys/bs.gif)