for 1900-01-01 to 1900-02-28 there is returned a wrong weekday. reason: 1900
is considered as a "leap year", but it is definitely not.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm...lic.excel.misc

for 1900-01-01 to 1900-02-28 there is returned a wrong weekday. reason:
1900
is considered as a "leap year", but it is definitely not.

It's a known bug...

http://support.microsoft.com/kb/214326

Rick

It's a known problem, I wasted my very first day on Excel on that very item.
Told my boss and he and whoever was visiting him laughed at me since everyone
knows that. So don't expect Microsoft to fix it. Just don't use any dates before
March 1st, 1904 and you will be okay in Microsoft's eyes. In other words if you
want to do driver's licenses for really old people, or genealogy make sure that
you are using text dates. You can also look at John Walkenbach's pages
Extended Date Functions Add-In,
http://www.j-walk.com/ss/excel/files/xdate.htm

KB214330 XL: Description of the differences between the 1900 date system and the 1904 date system in Excel, This article describes
the two date systems and the problems that you may encounter when you use workbooks that use different date systems
http://support.microsoft.com/default.aspx?kbid=214330
--
HTH,
David McRitchie, Microsoft MVP -- Excel
My Excel Pages: http://www.mvps.org/dmcritchie/excel/excel.htm


"geradok" wrote in message ...
for 1900-01-01 to 1900-02-28 there is returned a wrong weekday. reason: 1900
is considered as a "leap year", but it is definitely not.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm...lic.excel.misc

So don't expect Microsoft to fix it.

The link I provided in my answer in this thread explains why Microsoft will
never fix the bug.

Rick

Thank you both, Mr Rothstein and Mr McRitchie for your fast reaction. Now I'm
proud to be one of the "everyones". GK

"David McRitchie" wrote:

It's a known problem, I wasted my very first day on Excel on that very item.
Told my boss and he and whoever was visiting him laughed at me since everyone
knows that. So don't expect Microsoft to fix it. Just don't use any dates before
March 1st, 1904 and you will be okay in Microsoft's eyes. In other words if you
want to do driver's licenses for really old people, or genealogy make sure that
you are using text dates. You can also look at John Walkenbach's pages
Extended Date Functions Add-In,
http://www.j-walk.com/ss/excel/files/xdate.htm

KB214330 XL: Description of the differences between the 1900 date system and the 1904 date system in Excel, This article describes
the two date systems and the problems that you may encounter when you use workbooks that use different date systems
http://support.microsoft.com/default.aspx?kbid=214330
--
HTH,
David McRitchie, Microsoft MVP -- Excel
My Excel Pages: http://www.mvps.org/dmcritchie/excel/excel.htm


"geradok" wrote in message ...
for 1900-01-01 to 1900-02-28 there is returned a wrong weekday. reason: 1900
is considered as a "leap year", but it is definitely not.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/comm...lic.excel.misc

Good to see that that document http://support.microsoft.com/kb/214326
has been more truthfully updated, as to the real reasons why it is not updated.
Perhaps they should include a real astrological Julian Calendar (not the IBM one).

"Rick Rothstein (MVP - VB)" wrote in message ...
So don't expect Microsoft to fix it.

The link I provided in my answer in this thread explains why Microsoft will
never fix the bug.

Rick