On Fri, Jul 8, 2011 at 7:31 PM, Jim Lemon wrote:
> Hi folks,
> I have been tormented for some time by Excel's habit of exporting dates to
> CSV files as mm/dd/ format even if the dates are formatted dd/mm/ in
> the display. What's worse, if there are dates that are of ambiguous
> (6/6/2011
On 07/09/2011 06:26 PM, (Ted Harding) wrote:
...
I would not dare to suggest the above exchange for inclusion in
the Fortunes package. Fortunes are supposed to bring us joy.
But there is perhaps scope for a package Misfortunes.
Then, when things are not going well, one can enter
source(misfo
On 09-Jul-11 08:08:56, Duncan Mackay wrote:
> At 09:31 09/07/2011, you wrote:
>>Hi folks,
>>I have been tormented for some time by Excel's habit of exporting
>>dates to CSV files as mm/dd/ format even if the dates are
>>formatted dd/mm/ in the display. What's worse, if there are
>>dates
At 09:31 09/07/2011, you wrote:
Hi folks,
I have been tormented for some time by Excel's habit of exporting
dates to CSV files as mm/dd/ format even if the dates are
formatted dd/mm/ in the display. What's worse, if there are
dates that are of ambiguous (6/6/2011) and unambiguous (16/
Hi folks,
I have been tormented for some time by Excel's habit of exporting dates
to CSV files as mm/dd/ format even if the dates are formatted
dd/mm/ in the display. What's worse, if there are dates that are of
ambiguous (6/6/2011) and unambiguous (16/6/2011) format in the same
column
5 matches
Mail list logo
