Leap Year Validation

'***************************************************************** '* Function Name : bIsLeapYear * '* Created By : Thomas A. Cassano * '* date : 00/00/97 * '* Purpose : * '* Arguments : * '* Returns : Boolean * '* Comments : None * '***************************************************************** Function bIsLeapYear(dDate as date) as Boolean bIsLeapYear = ((Year(dDate) Mod 4 = 0) _ And (Year(dDate) Mod 100 <> 0)) _ Or (Year(dDate) Mod 400 = 0) End Function


Comments

  • Another way to check for Leap Year

    Posted by Legacy on 12/10/1999 12:00am

    Originally posted by: Rick Rothstein

    First of all, you should only have to pass the year in quesiton into the function, not a specific date. If you only have a date, pass Year(TheDate) into this:

    Function bIsLeapYear(TheYear As Integer) As Boolean
    bIsLeapYear = (DateSerial(TheYear, 2, 29) <> _
    DateSerial(TheYear, 3, 1))
    End Function

    Reply
  • for Current Month Last Day...

    Posted by Legacy on 09/22/1999 12:00am

    Originally posted by: Yon-Jin, KYUNG

    ' Return Last Day of Current Year and Month
    Function fnc_Month_LastDay(intYearValue As Integer, intMonthValue As Integer)

    Select Case intMonthValue

    Case Is = 1, 3, 5, 7, 8, 10, 12
    fnc_Month_LastDay = 31

    Case Is = 4, 6, 9, 11
    fnc_Month_LastDay = 30

    Case Is = 2
    fnc_Month_LastDay = IIf(IsDate(CStr(intYearValue) & "/2/29"), 29, 28)

    End Select

    End Function

    Reply
Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Instead of only managing projects organizations do need to manage value! "Doing the right things" and "doing things right" are the essential ingredients for successful software and systems delivery. Unfortunately, with distributed delivery spanning multiple disciplines, geographies and time zones, many organizations struggle with teams working in silos, broken lines of communication, lack of collaboration, inadequate traceability, and poor project visibility. This often results in organizations "doing the …

  • With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time coding instead of waiting for the dreaded application redeploy to finish. Every time a developer tests a code change it takes minutes to build and deploy the application. JRebel keeps the app server running at all times, so testing is instantaneous and interactive.

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds