Hi

Something for the weekend:

OI 9.4.0

Input field is data type DATE with Conversion = D4.E and Validation = (DE).

Users have become very used to entering dates without the slash.dot ie. when 230421 is entered the date is correctly converted to 23.04.2021.

This works fine up to 23.04.2029 (by entering 230429). But entering 230430 results in a converted value of 23.04.1930 - one hundred years ago. Oops.

Is this just something to live with or is there a reason for it?

Thanks,

Nick

Hi

Something for the weekend:

OI 9.4.0

Input field is data type DATE with Conversion = D4.E and Validation = (DE).

Users have become very used to entering dates without the slash.dot ie. when 230421 is entered the date is correctly converted to 23.04.2021.

This works fine up to 23.04.2029 (by entering 230429). But entering 230430 results in a converted value of 23.04.1930 - one hundred years ago. Oops.

Is this just something to live with or is there a reason for it?

Thanks,

Nick

Y2K pivot date?

Don Bakke

SRP Computer Solutions, Inc.

It's an old longstanding Pick takeaway. More modern implementations allow you to set the boundaries at which the century mark appear. I don't think it has been slipped into the product so the easiest fix is a UDC.

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft

Thanks chaps. So it's not just me.

A UDC would be fine excepting for the trillions of date fields already in the dictionaries, and sooo many screens to wade through and recompile. I think I may just instruct users to type in the dates properly.

View this thread on the Works forum...