>>>>>>Why do you think she would not allow the entry of 24:00?
>>>>>
>>>>>I think by 'normal' clock time the next time after 23:59 is 00:00. 24:00 is same as 00:00. There is not a time of 24:01 -- it would be confusing to see 24:00 and then 00:01 when the seconds ticked by... Time goes from 00:00 to 23:59 each day.
>>>>
>>>>My problem is that, since I ignore seconds, the minute between 23:59:00 and 23:59:59 is "not accounted" for. The data set by VFP is used by the .NET application: compares the current time with the time set by VFP. So, the .NET application could be reading the current time as 23:59:30 and the logic will tell the problem that this is outside of the day hours/minutes (00:00 to 23:59). But as I type this, I am thinking of the following "solution" When converting the time set by VFP (e.g. 23:59) in the .NET application, I could add the seconds part of 59 (automatically). Therefore, the entire range of time will be accounted.
>>>>Thank you.
>>>
>>>Of course the next question you may need to ask -- to what day does midnight belong? The 00:00:00 notation would suggest that midnight is the beginning of a day, whereas the 24:00:00 notation would suggest it is the end of a day.
>>
>>No, this question would not come up since I decided NOT to use the 24:00:00 but rather 23:59:59.
>
>In doing so, you've also avoided related "can of worms":
>* where does noon belong? is it the end of the first half of the day, or beginning of the latter half?
>* question of the beginning of a time period and the end -- 24:00:00 notation would suggest that first hour of the day would be 00:00:01 to 01:00:00 inclusive.

Another question would be "Why does your day have 25 hours?" as that is the number of hours from 0 to 24 :)