Datetime problem, the last two digits of the year changes automaticly to something else when entering a year

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

Comment

Load more comments

Chris Pollach @Appeon
Monday, 2 December 2024 19:18 PM UTC

Hi Michael!

My guess ATM is that it "might" be a "Region" setting bug.

If you can create a simple test case PB App for this issue, please open a Support Ticket & attach the test case.

This will allow Engineering to "hone it" on the problem.

Many thanks in advance!

Regards .. Chris

Helpful 0

Michael Doescher
Tuesday, 3 December 2024 10:34 AM UTC

Hi Chris,

that's our problem. We just can't reproduce the error to create a test case.

We were just hoping someone has some idea what to look for.

Kind regards

Mike

Chris Pollach @Appeon
Tuesday, 3 December 2024 13:07 PM UTC

FWIW: I would then look at your Apps code around the DW Control in events like the Key, EditChanged, Other, etc. to see if there is code trying to manipulate / block the normal DW's data entry processing.

There are no comments made yet.

Michael Doescher
Monday, 2 December 2024 12:46 PM UTC

Our format is dd.mm.yyyy

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.

Miguel Leeuwe
Monday, 2 December 2024 12:52 PM UTC

so it's not an edit mask but simply a format?

Resolved Datetime problem, the last two digits of the year changes automaticly to something else when entering a year