Jump to content
Gold Sponsor: Data-Way IT-Consulting, Austria

  • Date/Time Functions

    Date/Time Functions

    Function Description
    CDate Converts a valid date and time expression to the variant of subtype Date
    Date

    Returns the current system date

    Please see the note below and refer also to CurDate()

    DateAdd Returns a date to which a specified time interval has been added
    DateDiff Returns the number of intervals between two dates
    DatePart Returns the specified part of a given date
    DateSerial Returns the date for a specified year, month, and day
    DateValue Returns a date
    Day Returns a number that represents the day of the month (between 1 and 31, inclusive)
    FormatDateTime Returns an expression formatted as a date or time
    Hour Returns a number that represents the hour of the day (between 0 and 23, inclusive)
    IsDate Returns a Boolean value that indicates if the evaluated expression can be converted to a date
    Minute Returns a number that represents the minute of the hour (between 0 and 59, inclusive)
    Month Returns a number that represents the month of the year (between 1 and 12, inclusive)
    MonthName Returns the name of a specified month
    Now

    Returns the current system date and time

    Please see the note below and refer also to CurDate()

    Second Returns a number that represents the second of the minute (between 0 and 59, inclusive)
    Time

    Returns the current system time

    Please see the note below and refer also to CurDate()

    Timer Returns the number of seconds since 12:00 AM
    TimeSerial Returns the time for a specific hour, minute, and second
    TimeValue Returns a time
    Weekday Returns a number that represents the day of the week (between 1 and 7, inclusive)
    WeekdayName Returns the weekday name of a specified day of the week
    Year Returns a number that represents the year

     

     

    Note: When being used within a call routing script all date and time functions refer to the regional settings of the SwyxWare Service Account Windows user. All SwyxWare Services run with the privileges and configuration of this user, as do call routing scripts.

     

    If you use these functions outside the SwyxWare in a common VBScript file these functions refer to the regional settings of the current logged in Windows user.

     

    If you need to refer to the current script user's location (timezone) within a call routing script you need to use the provided GSE build in functions or use functions from the Server Script API.

     

    By using SetLocale you can modify the regional settings for the current script.

     


    Tom Wellige
     Share


     Share




×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and have taken note of our Privacy Policy.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.