I think the statement "There is no time without a date" applies if you are looking at the period between two times, but you can have and benefit from a TIME data type. For example, when selecting a reporting period, I allow users to enter the start and end date and time. With VFP, you can use the datetime field for this, but it is a little confusing for end users to figure out how fill up a datetime field. This means you have to split it into a date field and a time field, verify that the time entry is a valid time, combine the two into one string and convert the string into a datetime value. This would be easier if there was a built in TIME data type.

BTW, thank you and all the other respondents for the suggestions. These are good ideas and will solve the problem. Since VFP has a lot of powerful built-in fuctions, I thought it may have a simpler way for handling time values, but I guess it does not.

Mon