Claudine, If you can write a WHERE clause that finds all the bad dates, you should be able to write an UPDATE that fixes them.
Are all the wrong dates off by exactly a century? If not, you will have to make your WHERE clause more complicated, and do this more than once. SELECT datecolumn FROM tablename WHERE datecolumn <= '01/01/1900' UPDATE tablename SET datecolumn = + (RDATE(imon(datecolumn), iday(datecolumn), (iyr4(datecolumn) + 100 )) + WHERE datecolumn <= '01/01/1900' Bill On Thu, May 24, 2018 at 9:50 PM, Claudine Robbins <[email protected]> wrote: > Hello all, > > > > I’m on latest release. Some null values in a date field on a form are > coming up 12/30/99, fully extended to 12/30/1*8*99! There are no values > in that field in the table and the field correctly takes whatever date is > inserted and saves it to the table. > > > > I switched from 2-digit year to 4-digit year a few months ago and wonder > if that’s when this started. I reloaded the database, ran it through > R:Scope and all is sound. > > > > Any ideas on how to fix this? > > > > TIA, > > > > Claudine > > -- > For group guidelines, visit http://www.rbase.com/support/ > usersgroup_guidelines.php > --- > You received this message because you are subscribed to the Google Groups > "RBASE-L" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
