Excel 2010 - Date arithmetic BEFORE 1900 (1774 up to 1900)

I need to compute the number of days/months/years on a group of dates from 1700 to 1900.  I've got about 100 dates I need to compute durations on.
How can I do this?
Example:  October 7, 1779 to January 13, 1800
How many days/months/years.
Who is Participating?

Improve company productivity with a Business Account.Sign Up

Patrick MatthewsConnect With a Mentor Commented:
VBA supports dates before 1900, but Excel does not.  So, you could roll your own function in VBA to do this.

It would be much easier to download John Walkenbach's Power Utility Pak add-in, though: http://spreadsheetpage.com/index.php/pupv7/home/

It includes functions that handle pre-1900 dates.
Saqib Husain, SyedEngineerCommented:
Try adding 400 years to all dates with a formula like this


and then you can get the date difference.
I created a few UDFs which you can test on the attached workbook. They require that the dates are entered as Text on the worksheet. You can either format the cells as Text or precede your entries with an apostrophe which has the same effect. If you wish to install the functions in your workbook I suggest that you drag the entire module 'DateMan' to your own project and then save your file in XLSM format.
You can change the sequence of year, month and day to your liking. Just change the sequence of the Nds enumerations to match what you enter in the cells you want evaluated. You can also change the Date separator, just below the enum just mentioned, before the actual code starts.
There are samples of how to call the functions on the worksheet.
These are the functions available:-
YEARDIFF, MONTHDIFF, DAYDIFF - These functions were created to allow you to calculate the years, months and days between two dates. They will work on modern days as well as on historical ones. Note that the MONTHDIFF can be used to count the entire difference in months. Please observe how it is deployed in the worksheet.
DATESERIAL / HDATESERIAL - The former is designed as a UDF to call the latter which is designed as VBA function. The HDATESERIAL gives a number to each day since January 1, 0000, also converting dates entered as Text. This would enable you to sort your entries by date.
Finally, there is HWEEKDAY which works very much like VBA's own WEEKDAY function, largely because it utilizes that function. If Sunday is the first day of the week (the WEEKDAY function allows you to select your first day of the week), Monday would be the second. Hence, the result you see in the worksheet confirms that Charlemagne was crowned on a Tuesday, on Christmas Day in the year 800. Perhaps this function will be useful to you in some way.
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Patrick MatthewsCommented:

I have not checked all of your UDFs, but your HDATESERIAL function has a logical flaw in how it handles leap years.

Specifically, a year ending in "00" is only a leap year if it is divisible by 400.  Your code has it backward: your code makes the years divisible by 400 a standard year, and the "00" years that are not evenly divisible by 400 leap years.  (Of course, Excel treats 1900 as a leap year--incorrectly--while VBA does not.)

Also, keep in mind that when the Gregorian calendar was adopted, there was a 10-day skip: 1582-10-04 was immediately followed by 1582-10-15.  Your UDF makes no adjustment for that, so any date calculation that spans that adjustment will be off by 10 days.


FaustulusConnect With a Mentor Commented:

It's all that late night hobbying that produces the errors. :-)
The wrong treatment of leap years in my procedure HDATESERIAL isn't one of them, though. Please take another look. Perhaps I am blind on that eye even in the light of morning.

The Gregorian skip is another can of worms. Thank you for pointing this out to me. I have added the function 'GregorianSkip' which makes this adjustment adjustable in view of the different dates on which different countries made different changes to their then calendars.

The attached version of the same file previously uploaded has one correction, a number of improvements - in addition to the above - and doesn't feature the HWEEKDAY function any more. In order to determine the weekday of Charlemagne's coronation one may not be able to work backward in leaps of 7 days from today because the precise number of intervening days is subject to some doubt where sovereigns, both wise, haughty and practical, gave or took a few unaccounted days at their whim (or the advice of their tax consultants) in order to stay abreast of science's latest enlightenment during the otherwise dark ages.
Patrick MatthewsConnect With a Mentor Commented:
For my prior comment, I used the following test cases...

=HDATESERIAL(1800,1,1)   ---->    657447
=HDATESERIAL(1800,3,1)   ---->    657507

Diff of 60, implying there is a Feb 29 (thus a leap year)

=HDATESERIAL(1900,1,1)   ---->    693972
=HDATESERIAL(1900,3,1)   ---->    694032

Diff of 60, implying there is a Feb 29 (thus a leap year)

=HDATESERIAL(2000,1,1)   ---->    730496
=HDATESERIAL(2000,3,1)   ---->    730555

Diff of 59, implying there is no Feb 29 (thus not a leap year)
FaustulusConnect With a Mentor Commented:
Yes, Patrick, it was the blindness. Thank you for your assistance.
I attach another version of the workbook which - I guarantee - has fewer errors now than it had this morning.
With three quarters of a million days gone by there are just too many ways to test and, it seems, too many ways of erring, too. I will keep on correcting while some one finds errors.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.