The information in this article applies to:
Moderate: Requires basic macro, coding, and interoperability skills. SUMMARY
This article explains how Microsoft Access stores the Date/Time data
type, and why you may receive unexpected results when you calculate or
compare dates and times.
MORE INFORMATIONStoring Date/Time DataMicrosoft Access stores the Date/Time data type as a double-precision, floating-point number (up to 15 decimal places). The integer portion of the double-precision number represents the date; the decimal portion represents the time.Valid date values range from -657,434 (January 1, 100 A.D.) to 2,958,465 (December 31, 9999 A.D.). A date value of 0 represents December 30, 1899. Microsoft Access stores dates before December 30, 1899 as negative numbers. Valid time values range from .0 (00:00:00) to .99999 (23:59:59). The numeric value represents a fraction of one day. You can convert the numeric value into hours, minutes, and seconds by multiplying the numeric value by 24. The following table illustrates how Microsoft Access stores Date/Time values:
To view how Microsoft Access stores Date/Time values as numbers, type the
following commands in the Immediate window, press ENTER, and note the results:
?CDbl(#5/18/1999 14:00:00#)Result equals: 36298.5833333333 ?CDbl(#12/14/1849 17:32:00#)Result equals: -18278.7305555556 To view the date and time of numeric values, type the following commands in the Immediate window, press ENTER, and note the results: ?CVDate(1.375)Result equals: 12/31/1899 9:00:00 AM ?CVDate(-304398.575)Result equals: 8/1/1066 1:48:00 PM Formatting a Date/Time FieldYou can format a Date/Time value to display a date, a time, or both. When you use a date-only format, Microsoft Access stores a value of 0 for the time portion. When you use a time-only format, Microsoft Access stores a value of 0 for the date portion.The following table illustrates how Microsoft Access stores Date/Time values and how you can display those values using different formats: NOTE: The default format for a Date/Time value is General Date. If a value is date-only, then no time is displayed. If the value is time-only, then no date is displayed.
Calculating Time DataBecause a time value is stored as a fraction of a 24-hour day, you may receive incorrect formatting results when you calculate time intervals greater than 24 hours. To work around this behavior, you can create a user-defined function to ensure that time intervals are formatted correctly.Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact a Microsoft Certified Solution Provider or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Solution Providers, please see the following page on the World Wide Web: http://www.microsoft.com/mcsp/For more information about the support options available from Microsoft, please see the following page on the World Wide Web: http://www.microsoft.com/support/supportnet/overview/overview.aspTo calculate and format time intervals correctly, follow these steps:
43848 Seconds Comparing Date DataBecause dates and times are stored together as double-precision numbers, you may receive unexpected results when you compare Date/Time data. For example, if you type the following expression in the Immediate window, you receive a False result even if today's date is 3/31/1999:? Now()=DateValue("3/31/1999")The Now() function returns a double-precision number representing the current date and time. However, the DateValue() function returns an integer number representing the date but not a fractional time value. As a result, Now() equals DateValue() only when Now() returns a time of 00:00:00 (12:00:00 A.M.). To receive accurate results when you compare date values, use one of the functions below. To test each function, type it in the Immediate window, substitute the current date for 3/31/1999, and then press ENTER:
?Date()=DateValue("3/31/1999") ?Int(Now())=DateValue("3/31/1999") Comparing Time DataWhen you compare time values, you may receive inconsistent results because a time value is stored as the fractional portion of a double-precision, floating-point number. For example, if you type the following expression in the Immediate window, you receive a false (0) result even though the two time values look the same:var1 = #2:01:00 PM#When Microsoft Access converts a time value to a fraction, the calculated result may not be the exact equivalent of the time value. The small difference caused by the calculation is enough to produce a false (0) result when you compare a stored value to a constant value. To receive accurate results when you compare time values, use one of the methods below. To test each method, type it in the Immediate window, and then press ENTER: Add an associated date to the time comparison: var1 = #1/1/99 2:01:00 PM#Convert the time values to String data types before you compare them: var1 = #2:01:00 PM#Use the DateDiff() function to compare precise units such as seconds: var1 = #2:01:00 PM# REFERENCESFor additional information about calculating date and time values, please see the following article in the Microsoft Knowledge Base: Q210604 ACC2000: Functions for Calculating and Displaying Date/Time ValuesFor more information about how to format Date/Time data types, click Microsoft Access Help on the Help menu, type format property - date/time data type in the Office Assistant or the Answer Wizard, and then click Search to view the topic. Additional query words: inf
Keywords : kbprg kbdta AccCon TblDatyp KbVBA |
Last Reviewed: November 23, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |