Hello,

>
> Do you need the high resolution for your application? If not, your

could

> always round or truncate the Linux timestamp before inserting it.
>

Thats the problem. The server assigns the value of the timestamp. This
way I have not to depend on the client date and time. On Linux the
precision of the timestamp is 1/10000 second, on Windows 1 second.
When reading the value of the (Linux FB) server the Linux high
precision gets lost on a Windows client by the FB client function
isc_decode_timestamp. I think this is bad behaviour.

> What are you trying to do? I mean, how do you want to use the

timestamps?

>

As initally written I use the timestamp for comparisment if a record
has changed between my start of editing and committing the changes
(for this I use a userid (integer) and a timestamp). Reading and
committing are done in seperate transactions. After committing I check
the rows affected. This value should be one.
I know I could/should use RDB$DB_KEY but this involves a rewrite of
the application.

Thanks,

Roy Damman