Re: Date Types and Time Granularity

Force all the dates to have the same time? Maybe run the values through the datevalue() function to strip out time values (time is midnight by default, I think).

Just a quick thought.
Jon M

Randy Yates wrote in message <392EB190.DADCB1D2_at_207.87.184.178>...
>Hello Database Gurus,
>
>In the current database I am designing under Access 97, I initiallly
>used my own date types for dates (which was simply an 8-character
>string representing the date in the format "YYYYMMDD"). I later changed
>these to use Access's date type since that makes auto-generating forms
>and reports much easier.
>
>However, I now realize my initial reason for not using the Access date
>type. Access date types have granularity down to the second since it
>is in reality a date/time field. However, I have some tables that need the
>*date* and not the "date/time" to be part of the primary key. To simplify,
>let's just say the date *is* the primary key. Then I have the situation
>where multiple entries in the table for the same day are not allowed.
>
>How do I bridge this conflict between needing a date type with day
 granularity
>with Access's convenience in using date/time fields? Must I forego the
>convenience?
>--
>% Randy Yates % "I met someone who looks alot like you,
>%% DIGITAL SOUND LABS % she does the things you do,
>%%% Digital Audio Sig. Proc. % but she is an IBM."
>%%%% <yates_at_ieee.org> % 'Yours Truly, 2095', *Time*, ELO
>http://207.87.184.178/index.htm
Received on Fri May 26 2000 - 00:00:00 CEST