More musing on dates: Depending on whether you typically are entering past dates (like birth dates) or future dates (like mortgage payoff dates), and how far away from the present those dates might be, there may even be databases where 19 is no longer the best default CENTURY, but 20 would make more sense. And, by the same criteria, you might want to consider bumping the century threshold YEAR to a higher number.
For example, if you are entering birth dates of youth in the town soccer league, you are unlikely to have any players who were born in the years 1901 through 1929. But if you are entering birth dates of players in your shuffleboard league, you may have quite a few. For the 8 year old soccer player, if you enter 10/6/02, you'll make him 108 if your Century is 19 and your threshold year is above 30. And for the shuffleboard player who is 75 years old, if your Century is 19 and your threshold is 30, data entry of 10/6/35 will put his or her birthday in the year 2035. Bill On Fri, Sep 17, 2010 at 3:04 PM, Bill Downall < [email protected]> wrote: > Howard, > > You have your DATE SEQUENCE setting wrong. It should be set to two Ys, not > 4. When it is four, you are requiring that on data input, all four digits of > the year must be entered. > > Here is what you should have: > > R>sho date > DATE format MM/DD/YYYY > DATE sequence MMDDYY > Century threshold YEAR is 30 > Default CENTURY is 19 > > Bill > > On Fri, Sep 17, 2010 at 2:58 PM, Howard Langfus > <[email protected]>wrote: > >> Hello list. I am using the latest version of 9(32). Settings include >> century = 19 and year = 30. Having a problem filling in the correct year on >> all forms created under 7.6. If I create a new date field under v9 it fills >> in properly. Typing show var at the R> lists dates correctly. >> >> At present <enter>ing a date such as 9/17/10 on a form yields 9/17/0010, >> not the expected 9/17/2010. >> >> A possible solution I came up with is to: >> 1. Create new date columns, >> 2. Copy the date record information from the old columns to the new ones, >> 3. Rename the original columns, and >> 4. Rename the new columns back to the original column names. >> >> Now for my 2 part question. 1-Is there a better way to accomplish this? >> 2-How to “copy” the data in each record to the new columns? What steps are >> required to update the rows in the new columns? >> >> TIA for you help. >> Howard >> >> >> >
