I think you can change the pivot year. If so - change the pivot year to something that makes sense (00? or 99) Then go and search for dates <= pivot year then apply to the selection extracting and saving the date with an explicit year (19xx I assume)
On Thu, 25 Aug 2016 13:51:27 -0400, Eric Naujock wrote: > This database started out life in 4D back in 1985. As a result there > is a a lot of data that dates prior to 6.7. As a result I have a lot > of dates that are stored in 2 digit formats that have never been > converted to 4 digit years. But now I am showing people born in 2032 > and having died in 1987. This kind of messes up the statistics and > makes the reporting fail miserably. What am in need of doing is > finding the proper year and being to define it in mass for all the > records in the database so that I have no 2 digit years. > > The code that I used as an example I thought would do it by using > string to convert the date to an ISO format then using date to > convert the string date back to a proper date. The difficulty I am > running into is that I have a ton of 2 digit dates years in the > system that I need to get fixed into 4 digit years and I am looking > for a relatively safe an effective way to do this. Ideally I would > like to be able to block the ability to just enter 2 digit years and > require 4 digit years. > > ----------------------------------------------------------------------- > > MacCafe > 4405 Talmadge St. > Toledo, OH 43623 > Eric Naujock - ACSA 10.2, 10.3, 10.4 Apple - ACTC 10.5, 10.6, 10.7, > 10.8, 10.9, 10.10 > http://www.mac-cafe.com > email: e <mailto:[email protected]>[email protected] > <mailto:[email protected]> > AOL IM: erlic > > > >> On Aug 25, 2016, at 1:29 PM, Timothy Penner <[email protected]> wrote: >> >> Hi Eric, >> >> I think the pivot year has been 2030 for quite some time, at least >> since 4D v6.7, see here: >> http://www.4d.com/docs/CMU/CMU00392.HTM >> "By default, 4D sets the century to be the 20th century and uses 30 >> as pivot year. " >> >> I had assumed dates were stored in 4 digits and that the default >> century only affected data entry not stored values (i.e. it converts >> 2 digit dates to 4 digits; thus saving 4 digits to the database)... >> >> Does changing the default century change the data you already have >> stored? Like if you set the default century to 25 does it show that >> this person died in 2532 and was born in 2487? If so, then you could >> probably set the default century to 25 and then query for all dates >> with a year >2400 and then reset the year for the records you find. >> >> -Tim >> ********************************************************************** >> 4D Internet Users Group (4D iNUG) >> FAQ: http://lists.4d.com/faqnug.html >> Archive: http://lists.4d.com/archives.html >> Options: http://lists.4d.com/mailman/options/4d_tech >> Unsub: mailto:[email protected] >> ********************************************************************** > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > FAQ: http://lists.4d.com/faqnug.html > Archive: http://lists.4d.com/archives.html > Options: http://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
