Can you try the following transform in your machine, I have included your data and added two new whole years 2022 and 2023, at my end none has any issues, can you try and see if you get the issue?
Well that mean, there is something wrong at your side, if you are using Windows OS then please check if your system need any updates, since Microsoft rolls out update quite often.
A part from that, since we can’t reproduce the issue you are having, we can’t do anything.
You did not say, how is that first file, which started all this, is working? did you do any change or it was like next time when you accessed it is working? or it worked after restart of the machine or what?
I can’t think of anything else, the file I setup for you, is working fine at my end as you have seen the screenshot.
Maybe some other users can download the transform and post their finding in here? to find out that it is just with you or others have the same issue?
Well, first of all… this is an amazing software
And you have all my gratefulness for the effort in support
I’m kind of used to be “the only user” with problems, as many software don’t work well with localization or other specific characteristics
some clarification:
a) I’m testing this in 2 PC’s
b) Only 1 Date, of September, each day, fails.
You can see the first images.
c) I just run 15.706 rows.
All dates from 1.jan.1990 to 31.Dec.2032
guess what… All the dates that fail are SUNDAYS…
AS Gordon said to Robin “you’re not allow to belive in coinsidences”
I repeat, only the first sunday of each September fails to convert
These are the only dates that failed, from 1.jan.1990 to 31.Dec.2032
Well, that is very strange. We call a function in the Qt library to do the conversion ( QLocale::toDateTime()). But I can’t reproduce the problem here, even if I set my locale to Spanish/Chile. Also no other reports of this issue.
Glad you found the cause. I didn’t seem to have this issue when I set my Locale to Spanish/Chile in Easy Data Transform Preferences window. So perhaps DateTime format uses the OS locale instead. I will look into that.
Ok, so I can reproduce the problem encountered by @SullyPanda76cl if I change my Windows time zone to Santiago. It disappears if I change it back to London. So mystery solved and it isn’t a bug. I will add a note to the Date Time Format documentation.