Hi Jeff,

>> Long time no talk! How's it going over there across the Pacific?
>>
>
> It is our quiet season here, despite the clear blue sky and the crystal
> clear water of the lagoon ... I sound like a travel brochure.  It's
> quiet because our major markets for visitors are the Aussies and the
> Kiwis and theoretically their weather is pretty good this time of year.
> And we are also supposed to be in the hurricane season (touch wood).
>
> Quiet means more time shackled to the computer

That's no good. Maybe Tim will have to bring forward his whirlwind tour of
the world, and visit you first to keep you on your toes.

Have a great weekend mate!

Adam.

Hi Tim,

Thanks for your reply...

> Ahh, okay.  In that case, use something like this:
>
> SELECT CAST(<TimeStampColumn> AS TIME)-CAST('00:00:00' AS TIME)
> FROM MyTable

Thanks for your help with this. So - to confirm, there really isn't a direct
way to access that value. (ie - we need work arounds like this). That's not
a problem - as long as I know.

Have a great weekend mate, and keep up the good work!  

Cheers

Adam.

Adam,

<< That's no good. Maybe Tim will have to bring forward his whirlwind tour
of the world, and visit you first to keep you on your toes. >>

That's the first place we're stopping.  Have you seen pictures of his home ?
It's like you've died and gone to heaven.  It's 5 degrees (F) here in the
Buffalo area today.

--
Tim Young
Elevate Software
www.elevatesoft.com

Jeff,

<< In DBSYS v3.30 this:-

SELECT CAST(CURRENT_TIMESTAMP AS TIME)-CAST('00:00:00' AS TIME)
FROM MyTable TOP 1

... always gives the same number of milliseconds UNLESS you Unprepare each
time you run it.  >>

Yes, DBISAM behaves differently than with ElevateDB, which evaluates the
CURRENT_TIMESTAMP like a true function, returning a different value for each
call.

--
Tim Young
Elevate Software
www.elevatesoft.com