Personally, I have often wished for a separate time type.
DateTime works, but sometimes you want only the time part.
It is not only about data storage, but also about doing all the corresponding calculations.
Of course, as long as nothing specific exists, you could create a class for that - but it would save some work if something built-in already existed.
BTW, I would make that 4 bytes too, but that would be one each for hours, minutes, seconds, 1/100 seconds.
>VFP7
>
>I have a field of type DATE in a given table.
>
>It would be nice to not only have the date but also the time of a given transaction.
>
>If I change the type from DATE to DATETIME I'll have to change lines of code in several placed to take that change into consideration.
>
>Now here's the thing. I just thought that perhaps a new field of type C(4) could be added instead of changing the DATE to a DATETIME. The name of that new field could be HourMinute.
>
>For example if the time of transaction is 3.51 pm the characters stored would be "1551".
>
>Does that make sense or is it really worth it to change to a DATETIME and do all the necessary fixes?
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
