2020 dates not parsing correctly in Set Value To

[ddhsoftwareadmin]

Hey everyone,

I was able to verify a reported bug in the iPad version now that 2020 is among us. The app always assumed when dealing with two digit years that anything with /00, /01, .. /19 in the year column was after 2000, but anything from /20 on was assumed to be 1900 (ie, 1920, 1921, etc). I have made this change and am going to release a beta and hopefully a new build will be out in the next month or so. In the meantime, don't use the Set Value To.. function for setting dates from 2020 on. Very sorry about this. When I wrote HanDBase, 2020 seemed a lifetime away and 1920 felt more realistic a date to use

[edwin2011]

Thnx for addressing this. Is this "bug" also in Android version?

[HermanD]

If I look at the Android calendar, the last date that is presented is 01-01-31 so ten years to go
before whe have the same problem as IOS.

If HandBase is then still alive??

regards
HermanD

[parishdm@att.net]

I've noticed a problem with date fields in one of my older databases that's followed me from Palm through several versions of iPhones over the past 20 years. Some of the date values appear as the ISO Date format (preferred) YYYY-MM-DD with the "-" delimiter and some appear in MM/DD/YY format with the "/" delimiter. I also noticed a number of the "1/1/00" dates, but none that were entered as being after 2020/01/01.

Is there any plan on the drawing board to offer an ISO Standard date format option? That is much better for sorting dates. Seems that if I chose a view with a date-sorted field, they sort in text order rather than numerical order.

Dale