Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Over midnight causes bug
Message
 
To
04/07/2001 11:20:26
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00526579
Message ID:
00526779
Views:
15
To coin a phrase:

D'oh!

Cheers,

Andrew

>Andrew,
>
>>Hi Gavin,
>>
>>The datetime() approach works well when the resulution required is 1 second or greater. Seconds() returns down to 100ths of a second.
>>
>>On a different note, remember that you can use strict date literals if your code below read
>>
>>dtStartTime   = {^2001-07-04 11:59:59 PM}
>>dtEndTime     = {^2001-07-04 12:00:01 AM}
>>nTotalSeconds = dtEndTime - dtStartTime
>>
>>it would work regardless of SET("DATE") - note the caret before the year.
>>
>
>>snip<
>
>Except the day for dtEndTime should be '05' rather than '04'. Otherwise you get -86398. <g>


If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?


From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."


All my FoxTalk and other articles are available on my web site.


Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
Previous
Reply
Map
View

Click here to load this message in the networking platform