That's a big change from Flex 1.5 to Flex 2.0 if it is so.

I really doubt it. It must be some kind of bug in Flex 2.0 date
decoding function . 

Reply via email to