Hi Albert,

I'm not sure why you originally posted this question, but from a data storage standpoint I would consider the following, Microsoft's SQL Server does not recognize 24:00 as a valid time, it only recognizes 00:00 through 23:59. So if one were inputting data to SQL Server it would be valid to submit "12/05/2002 23:59" or "12/06/2002 00:00" but it will not accept "12/05/2002 24:00" on a datetime or smalldatetime field, instead it would indicate the value is not consistent with the data type or something like that.

John



>Hi Alex,
>
>Thanks for the "Er" as I had not realized that military time had no colon. I was looking in a book on international apps (old one by Steven Black) and it showed times around the world with various separators and ranges but did not actually show military time. Seems like "2400" is acceptable as well but not entirely correct (one of the links posted here said it is acceptable because it is easier to say than 0000). Thanks agaoin.
>
>>>Okay, a quick one - is 12:00 midnight "00:00" in military time or is it "24:00" (you can tell I have never been in the military)? Likewise, is the range of acceptable values "00:01" to "24:00" or "00:00" to "23:59"? And finally, is it possible that both 00:00 and 24:00 are acceptable values?
>>>
>>>Albert
>>
>>Er, "00:00" is not military time but 24-hr time. The military uses no colon, (e.g. 1200, 1324, as opposed to 12:00 and 13:24). 24hr time is used in many countries (probably most countries around the world). And as said in this thread, it's 00:00, not 24:00 (goes from 00:00 to 23:59).