>>If a second is being added then shouldn't gt + 1 yield 01/07/2012 00:00:01 ?
>>
>>Update: Not enough coffee.... So gt+1 should still be 30/06/02012 23:59:59 ?
>
>Saw it on TV - the display goes from 2012-06-30 23:59:59 to 2012-06-30 23:59:60 and then to 2012-07-01 00:00:00

No idea what it actually does. My comment referred to what I thought it *should* do :-}

>>>A leap second is being added at midnight tonight, June 30 2012. VFP (and probably most of the world's software) doesn't handle it properly:
>>>

>>>gt = {^2012-06-30 23:59:59}
>>>?gt + 1 && returns 2012-07-01 00:00:00
>>>* It should return 2012-06-30 23:59:60
>>>

>>>Just a little something (i.e. huge can of worms) to be aware of if you need second-accurate time calculations that span the leap second.
>>>
>>>Some systems are weirdly affected and may crash. For instance, the last leap second caused the SlashDot web site to crash: http://it.slashdot.org/story/12/06/30/2123248/the-leap-second-is-here-are-your-systems-ready