Hi Aldrich,

I'm not familiar with MySQL, so this is a shot in the dark.

If MySQL has an internal function that returns miliseconds, you might want to store that in a separate field from the records' date/time.

If it doesn't have such functionality and its stored procedures have the ability to call the windows API, you might be able to get a hold of the timee. Failing this the next best thing would be to write an executable in assembler or C that would return that information and call it from a stored proc in MySQL. I say assembler or C because if you're looking for miliseconds time is likely to be important to you.

One possibility would be to generate the timestamp from the workstations, but I really don't think that you can sync workstations' times down to the milisecond, so chances are you run into problems - especially if this is part of a primary-key scheme.

If all you're looking for is to know the order in which records were added, why not use MySQL's internally-generated primary key? It's sequential. That and a datestamp with seconds precision should be good enough for most uses (unless you're dealing with subatomic particles or olympic athletes, but Aruba's more famous for her windy beaches than nuclear research or olympiads).

Have fun!

Alex


>Hi There,
>
>Is there a way to handle/retrieve milliseconds in a timestamp?
>
>Rgds,