[AccessD] A2K: Time diff calcs

Mark A Matte markamatte at hotmail.com
Wed Sep 15 08:19:55 CDT 2004


Maybe I missed something...but if you are already storing a start time...and 
an end time...do you need to store the seconds...can you just calculate the 
min/sec when you need to display or count?

Thanks,

Mark




>From: Gustav Brock <gustav at cactus.dk>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>Subject: Re: [AccessD] A2K: Time diff calcs
>Date: Wed, 15 Sep 2004 14:29:37 +0200
>
>Hi Darren and Stuart
>
>Except for very excessive processing, processing time will be
>negligible compared to the time for reading and, indeed, writing the
>data.
>However, should heavy processing be needed, process the values in Long
>variables even if they are stored as Integer.
>
>For short intervals, four minutes or less, the seconds could even be
>stored as Byte.
>
>/gustav
>
>
> > On 15 Sep 2004 at 21:06, Darren DICK wrote:
>
> >> Hi Arthur
> >> Many thanks for the tip and I agree. Store the seconds format when 
>needed.
> >> In the relevant table should the data type be Integer?
>
> > if you need more than 32767 seconds (a bit over 9 hours) you will need 
>to
> > use a long.
> > If you  don't need that much, it is debatable.  Integers take half the
> > storage of longs, but take a bit longer to process if you are 
>manipulating
> > them. Depends on whether you want to save on storage or optimise 
>processing
> > time.
>
> > However don't save them as singles or doubles.
>
> > --
> > Stuart
>
>--
>_______________________________________________
>AccessD mailing list
>AccessD at databaseadvisors.com
>http://databaseadvisors.com/mailman/listinfo/accessd
>Website: http://www.databaseadvisors.com





More information about the AccessD mailing list