At 07:19 AM 17/06/2004 +0000, you wrote:

>Hi,
>I have a timestamp field filled with the CURRENT_TIMESTAMP function,
>but when I convert it to a varchar I always see something
>like "16/06/2004 09:14.45.0000", where the milliseconds part is
>always "0000". I convert it doing Cast(DocDate as varchar(24))
>I think there are two possibilities:
>- CURRENT_TIMESTAMP correctly fill the field, but "Cast" doesn't work
> properly so it forgets my milliseconds.

No.

>- CURRENT_TIMESTAMP doesn't fill the field with milliseconds.

Yes. Current_timestamp cannot do better than the nearest second. This is
due to a UNIX limitation of some sort. You can get a timestamp with
accuracy to ten-thousandths of a second using the external function
GetExactTimestamp() that you will find in fbudf.

/heLen