This is caused by the regional settings of your computer. When you paste data into excel it is only a bunch of strings (not dates). Excel has some logic in it to recognize your current data formats as well as a few similar date formats or obvious date formats where it can assume it is a date.
For the first time and immediately do a repair of Excel (per instructions above). Re-install the add-ins. Open Excel and see if the add-ins work. If the add-ins still do not work, reboot again and run the Temp File Deleter a third time. Run all options. Run Windows Update.
![For For](/uploads/1/2/5/6/125605233/423991321.jpg)
When it is able to match your pasted in data to a valid date then it will format it as a date in the cell it is in. Your specific example is due to your list of dates is formatted as 'm/d/yy' which is US format. It pastes correctly in my excel because I have my regional setting set to 'US English' (even though I'm Canadian:) ) If you system is set to Canadian English/French format then it will expect 'd/m/yy' format and not recognize any date where the month is 13. The best way to import data, that contains dates, into excel is to copy it in this format. 2011-04-01 Which is 'yyyy-MM-dd', this format is recognized the same way on every computer I have ever seen (is often refered to as ODBC format or Standard format) where the units are always from greatest to least weight ('yyyy-MM-dd HH:mm:ss.fff') another side effect is it will sort correctly as a string.
To avoid swaping your regional settings back and forth you may consider writting a macro in excel to paste the data in. A simple popup format and some basic logic to reformat the dates would not be too difficult. Try formatting the column to just being a number. Dates are stored by Excel as numbers (e.g. 11th January 2011 is 40554 in Excel in almost all cases.) Anything that remains as a string hasn't been recognised as a date. You may have a further issue where your dates have been interpreted in dd/mm/yy format rather than mm/dd/yy.
If your 11-04-11 comes up as 40664 then it's 11th April; if it comes up as 40851 then it's 4th November. It would be much better to use an unambiguous format like 2011-04-11 (for 11th April) or 2011-11-04 (for 4th November).Date1904 property of Workbook can affect this – Jan 11 '11 at 23:56. The simplest solution is to put yy,mm,dd into the date formula by first extracting them with left, mid and right. In this case, assuming your input date is in A1: =date(right(A1,2)+100,left(A1,2),mid(A1,4,2)) Explanation of above: =right(A1,2) gets the last two digits in the cell (yy). We add 100 because it defaults to 1911 instead 2011 (omit +100 if it doesn't do that on yours) =left(A1,2) gets the first two digits in the cell (mm). =mid(A1,4,2) gets 2 digits in the middle of the cell, starting at 4th digit (dd). Why this happens in the first place: I come across this problem all the time when I import Canadian bank data into excel.
In short, your input date format does not match your regional settings. Seems your setting mean Excel wants date input as either DD-MM-YY or YY-MM-DD, but your input data is formatted as MM-DD-YY. So, excel sees your days as months and vice-versa, which means any date with day below 12 will be recognized as a date, BUT THE WRONG DATE (month and day reversed) and any date with day above 12 won't be recognized as a date at all, because Excel sees the day as a 13th+ month. Unfortunately, you can't just change the formatting, because Excel has already locked those day/month assignments in place, and you just end up moving what Excel THINKS are days and months around visually, not reassigning them.
Frankly, it is surprising to me there is not a date-reverse tool in excel, because I would think this happens all the time. But the formula above does it pretty simply. NOTE: if your dates don't have leading zeros (i.e. 4/8/11 vs 04/08/12) it gets trickier because you have to extract different amounts of digits depending on the date (i.e. 4/9/11 vs 4/10/11). You then have to build a couple if statements in your formula.
![Microsoft excel for mac 2011 Microsoft excel for mac 2011](/uploads/1/2/5/6/125605233/119249545.png)
They're restless. Users of Microsoft's who upgraded to Apple's OS X 10.11, aka, have become increasingly frustrated by repeated crashes of the Office applications, angrily denouncing Microsoft, and to a lesser extent, Apple, on the former's support forum. 'It's called Office '2016' because that's the expected date it 'might' work, although when in 2016 is not clear, assuming we are using the Gregorian calendar!' Wrote someone identified only as 'bluedolphin' in a Tuesday message on the dedicated to the crash issue. Related: As of late Wednesday, that thread had been viewed more than 39,000 times and contained nearly 400 messages, both very high numbers for the Office for Mac support forums. Most focused their ire on Microsoft.
'Light a fire under somebody's a to get a fix out, or at least a work-around,' urged 'MS Patsy' in a Monday reply to a Microsoft program manager who had posted on the thread last week. 'Now you know why I switched to all Mac products. Windows and Outlook are the only remnants of Microsoft JUNK that I'm left with.'
But some expanded their exasperation to include Apple. 'How is it remotely feasible that neither Microsoft (mostly at blame) or Apple (ignorance is not great customer service) had any proactive communication to NOT DOWNLOAD EL CAPITAN?' Asked a commenter labeled 'cxr341' on Tuesday. 'It would have been a simple correspondence: 'Hey, we see you use our new Office 2016 on Mac, there's a big OS X update coming, give us a bit of time until you download it.'
No harm, no foul.' The bulk of those reporting problems with Office for Mac 2016 began seeing the applications crash last week. The issue goes back further than that, however, with complaints first appearing July 10, just one day after Microsoft launched the production build of Office for Mac 2016 and Apple delivered its first public beta of El Capitan. Most of the crashes involve Outlook, the suite's email client, but other applications, including Word, Excel and PowerPoint, also regularly drop dead, either separately or when Outlook goes down. Computerworld staffers running Office for Mac 2016 on El Capitan-powered Macs have been affected as well.
Not everyone has had to deal with crashing productivity. An engineer who specializes on the Mac and works for a multi-national IT services firm reached out to Computerworld, saying that none of those in his workplace's pilot program had seen Office 2016 for Mac crash or freeze when running on El Capitan. On Wednesday, Microsoft issued a fix for a separate-but-related issue, one involving Office for Mac 2011, the new suite's predecessor. That problem had caused Outlook 2011 on El Capitan to crash when syncing with Exchange mail servers. An claimed to stop the crashes, and users commenting on Microsoft's support forums confirmed that they were again working without interruption. Not surprisingly, that prompted people running Office for 2016 to ask when their needs would be addressed.
'Where is Office for Mac 2016's fix?' Wondered 'Tony Lin8' on Wednesday. Microsoft was not ready to set a timetable for an Office for Mac 2016 update. 'Please stay tuned for the fixes for Mac Outlook 2016 on El Capitan,' wrote Faisal Jeelani, a Microsoft program manager, in the longest thread Wednesday. 'I will update this thread as soon as we have something to share. Thank you for your patience and understanding.' On, a different Microsoft program manager offered a bit more information.
'We have isolated the hang after crash/force quit that impacts all Office 2016 apps as well as Outlook 2016 repeated crash after launch,' Sunder Raman said yesterday. 'We are working with Apple on a solution, please stay tuned.' Previously, Raman had referenced working with Apple, as had a company spokeswoman, implying that the problem was within El Capitan or that the fault was shared by both companies. A third possibility, that Microsoft was simply gathering information from Apple, seemed more remote Wednesday after Apple released Beta 3 of OS X 10.11.1, the first expected update to El Capitan, to both developers and public testers. While the public beta's description only said that it was addressing stability, compatibility and security issues, the developer's version listed Office 2016 as one of two areas of focus, a clue that El Capitan is at least partly to blame for the crashes. Computerworld downloaded and installed the public preview of Beta 3 Wednesday, and although Office for Mac 2016 applications had not crashed since, it was too early to call the problem solved. After installing Beta 2 last week, Computerworld's Macs running the new suite were crash-free for approximately 36 hours, at which point crashes and application lock-ups resumed.