• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Datetime problem, the last two digits of the year changes automaticly to something else when entering a year

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

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

  1. New
  2. Issue
0
Votes
Undo
  1. Michael Doescher
    Michael Doescher
  2. PowerBuilder
  3. Monday, 2 December 2024 09:39 AM UTC

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

Create column dynamically in a datawindow
Profiling Trace View alternative?
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 2 December 2024 13:31 PM UTC
  2. PowerBuilder
  3. # 1

Hi Mike;

  When posting these type of questions, please always supply...

  • OS version & build
  • PB version & build
  • Regional settings being used

Regards ... Chris 

Comment
Load more comments
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. 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
  1. Helpful
Michael Doescher
  1. Michael Doescher
  2. 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
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. 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.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 2 December 2024 11:13 AM UTC
  2. PowerBuilder
  3. # 2

Are you using an edit mask / format? What's its value?

If you have and edit mask and it ends in yyyy, you should not type in 24, but 2024 instead.

Comment
Michael Doescher
  1. Michael Doescher
  2. 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.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 2 December 2024 12:52 PM UTC
so it's not an edit mask but simply a format?
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.