The lack of support for milliseconds in the timestamp (especially
since the storage is available) is definitely an issue for me. We
write an application that catalogs images, which produce dates with
millisecond precision. The key isn't the actual value per se, but
the relative value versus other images. If a digital camera can take
10 pictures within a second, we need to use the millisecond portion
to define the order.

If the database can sort the dates using the milliseconds, that will
be part of the battle, but we will still need to show the
milliseconds in the application. I suppose we could create another
column to store the millisecond portion for display purposes. Still,
its a hack and hopefully Firebird 2.0 will expose the millisecond
support.

If I can't use timestamps to store the change indicator, i'll likely
just use a generator; it should work well for this anyway.

Thanks all for the help!

Greg