Wow, that's strange. How is your computer's locale set up?
Thanks for the reply!
I am located in Austria, but my OS is in English (US), so all the date settings are m/d/y. The data is however in the local format d/m/y.
I did not experience this issue with excel files or csv. It only happened when I used the Microsoft Access Database for my source data.
Additional Info: If I change the settings in my OS and re-format the date and time to the local format (d/m/y) everything is fine again.
I have made it work with string parsing, or I can keep my entire OS in the new format. However, this definitely seems to be a bug.
1 of 1 people found this helpful
Yes I tend to agree. It should either use m/d/y or d/m/y but it shouldn't mix and match. Ultimately, I'd expect the second date to give you an error since it is an invalid date according to your OS locale settings.
It is a bit disconcerting to me, however, that your Access database is storing dates as string fields rather than actual dates. Excel and Text do not have data types per se, so that can often make sense, but Access does so that seems a bit strange.
Thanks for the input. However, my concern was the inconsistency and not a specific date format. Change of format within the same column is the issue.
Thanks and yes makes sense. Unfortunately I don't have control, but will speak with someone who might be able to address the formats in the DB. Thanks!