this:
first you have to grasp...seconds, which create minutes, which create hours,
which create days, etc....
I know that's not tough...but it's the basis for which all things in this
app will have bearing.
but back to the question whats the original goal/layout you are looking for?
you may have posted already, but a quick run-down of the final
application...
tony
-----Original Message-----
From: Jeff Small [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 24, 2004 1:24 PM
To: CF-Talk
Subject: Re: Quick Question, RE: Datatype and future date/time calculation
> use seconds in an integer field...
> they are easier to work with....
>
> using epoch time (01/01/1970 00:00:00.000)
>
> you can use that as a base, and do dateDiff's and dateAdd's using
> (now()) or a date in the future....to get seconds in between two events...
>
> if you need more code to look @ this to make sense of what im trying
> to explain let me know...
>
> tony
Just as a basic example, how would I start by allocating something 17 and a
half hours, then insert three entries into another table which total more
than 17 and a half hours (15.5, 5.75, and 6.5, which totals 27.75 on my
calculator) then calculate the overage?
I get the insert (kinda) for the original time (17 hours, 30 minutes, 0
seconds?) and I'm assuming the insert for the three "used times" would be
the same general insert, but it's the pulling out and calculating that's
kinda stumping me...I think...
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
