[AccessD] Re: Using Dates

Charlotte,

I have a function that I run that populates the table with about 100 years 
of data.  Since that is only a little over 36,500 rows, it is relatively 
small.  The only thing that has to be done then is to define holidays for 
each year.  After it is created, it makes handling dates so much simpler 
for end users and programmers alike.  ;-)

Robert

At 07:04 AM 1/30/2004 -0600, you wrote:
>Date: Thu, 29 Jan 2004 12:34:58 -0800
>From: "Charlotte Foust" <cfoust at infostatsystems.com>
>Subject: RE: [AccessD] Using Dates
>To: "Access Developers discussion and problem solving"
>         <accessd at databaseadvisors.com>
>Message-ID:
>         <E61FC1D4B1918244905B113C680BEA863125C0 at infoserver01.infostat.local>
>Content-Type: text/plain;       charset="us-ascii"
>
>Yes, it's a very effective tool for doing date filtering in queries and
>reports.  I've used it in data warehouse type applications and also
>where users wanted to be able to get results for the last 6 months and
>compare that to the same period last year or some similar kind of time
>frame slicing and dicing.  The biggest problem with it is creating the
>code to keep it updated.  I usually only updated it once a year to add
>the new year's values.
>
>Charlotte Foust