RE: datetime field

---- you wrote: > Jonathan pointed out to me offline that there's something called > DBINFO("utc_current") that might offer a solution. <Sigh> Guess I have to> read a manual again... Yes Dude, because that is in seconds, so you need to do something like: SELECT DATETIME(1970-01-01 00:00:00) YEAR TO SECOND + DBINFO("utc_current") UNITS SECOND FROM systables WHERE tabid = 1 > But it does beg the question: if there *is* a way of doing it, why doesn't > CURRENT work as expected? I think a stored procedure is seen as an object. An object can be timed, but outside the actual object. The timex command is very good for this. AB ---------------------------------------------------------------- Get your free email from AltaVista at http://altavista.iname.com