I am converting data from a legacy system that had some poor date editing. I am finding issues in the dates, most of which are solved.
One issue is the number of days in a month. For example they have a date of 11/31/2005, which throws an error when trying to convert to a standard date in Access. I added logic to identify legacy dates with more than the standard days in a month. It works for all months except February, in which case leap years have 29 days, non-leap years have 28. I know I could test for leap years by entering all leap years.
Before doing that I was wondering if anyone has a routine that if passed a numeric year like 2012, can identify it as a leap year or not.