DWUTKA at marlow.com
DWUTKA at marlow.com
Thu Mar 4 14:05:35 CST 2004
I would record the date/time field, versus recording the duration. The duration is simply the difference between the start and end time, and will display properly in the table itself. The 'duration' would still be stored as a date/time (or a double...technically the same....). Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Bryan Carbonnell Sent: Thursday, March 04, 2004 8:44 AM To: accessd at databaseadvisors.com Subject: [AccessD] How to Deal with Time Durations In a new app that I am creating, of which you will probably hear ALL about it over the next few weeks :), I have to keep track of event durations. Right now I have a field for the start time, and one for the duration. Both are Date/Time fields. The durations for the event can last from 1 second all the way up to many hours, and possibly even days. Should I actually be storing the start and end time and calculating the duration? The duration can be entered as either the actual duration or the actual end time. If you have done something like this, how have you handled it? Thanks, Bryan Carbonnell bryan_carbonnell at cbc.ca -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com