>>>>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.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham