Hi, we have a problem with the datetime columns and were hoping someone else has experienced this as well and knows why.
It suddenly happens at the costumer and here in house. We just can’t recreate it and are therefore at a loss what’s going on.
The only way to correct it, is to restart the program. If the costumer doesn’t catch it right away, the costumer saves bad data which is not good at all.
Example:
In a datetime field we have 01.01.2000
The costumer wants to change it to 01.01.2024
When the costumer goes to the two last digits and types in 24, the 2 is taken with no problem 01.01.2020 but when the 4 is put in, it suddenly changes to 01.01.2063.
This can be repeated and happens everywhere and if you put in 25, the 2 is taken with no problem 01.01.2020 but when the 5 is put in, it suddenly changes to 01.01.2073.
The customer has the feeling the two digits are added up but why it then ends with a three, we don’t know.
We would be very grateful if anyone has an explanation.
Kind Regards
Mike
When entering the 24, the cursor is on the right position.
Changing from 01.01.2000 to 01.01.2020 works fine.
In fact, it work almost all the time perfectly.
Just for some reason, one which we can't figure out, it suddenly doesn't work.
Then when editing the last two digits, der year jumps and changes as described.