Answers.Body: <p>There was an issue due to some refactoring around the handling of date fields to try to standardise them. This lead to a problem most notably in birth date fields in 4.7.16 but i'm guessing can be found elsewhere. This issue was raised <a href="https://issues.civicrm.org/jira/browse/CRM-19982" rel="noreferrer">CRM-19982</a> </p>
  
  <p>I suspect the same fix will most likely work for you. If you have a test site or would like to give a test a shot. I would recommend you look at the changes made to the files in the DAO directories here in the <a href="https://github.com/civicrm/civicrm-core/pull/9831/files" rel="noreferrer">Pull Request</a> and make the same changes on your server. </p>
  
  <p>That pull has been merged into 4.7.17 which will be released i think in the next week or so</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-04T08:37:31.347Z
Answers.Text: I applied the fix and it's working OK now, thanks again
Answers.UserDisplayName: Andy Clark
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-05T09:03:50.627Z
Answers.Text: Excellent good to hear Andy.
Answers.UserDisplayName: Seamus Lee
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-03-02T20:27:23.190Z
Answers.LastActivityDate: 2017-03-02T20:27:23.190Z
Answers.UserDisplayName: Seamus Lee
Body: <p>Entering a date has changed in 4.7.16 so the user can no longer drop down the year in order to select a year in the past.  Now they have to scroll through months to go backwards!  Imagine entering a date of birth of (say) 1967 - you have to go back 600 months!!  I'm assuming this is a bug, but rather a serious one from a user's point of view.  Does anyone know how this can be easily reverted to what it was before?  In the meantime I'm avoiding my users....</p>
  
  <p>I have raised problem CRM-20209</p>
  
Tags: <4.7><dates>
Title: Why has entering a date changed in 4.7.16? Can it be reverted?
ThreadText: # Why has entering a date changed in 4.7.16? Can it be reverted?
  
  (Asked by: username_0 on 2017-03-02)
  
  Entering a date has changed in 4.7.16 so the user can no longer drop down the year in order to select a year in the past. Now they have to scroll through months to go backwards! Imagine entering a date of birth of (say) 1967 - you have to go back 600 months!! I'm assuming this is a bug, but rather a serious one from a user's point of view. Does anyone know how this can be easily reverted to what it was before? In the meantime I'm avoiding my users....
  
  I have raised problem CRM-20209
  
  **Tags:** 4.7, dates
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2017-03-02. Score: 4
  
  There was an issue due to some refactoring around the handling of date fields to try to standardise them. This lead to a problem most notably in birth date fields in 4.7.16 but i'm guessing can be found elsewhere. This issue was raised [CRM-19982](https://issues.civicrm.org/jira/browse/CRM-19982)
  
  I suspect the same fix will most likely work for you. If you have a test site or would like to give a test a shot. I would recommend you look at the changes made to the files in the DAO directories here in the [Pull Request](https://github.com/civicrm/civicrm-core/pull/9831/files) and make the same changes on your server.
  
  That pull has been merged into 4.7.17 which will be released i think in the next week or so
  
  > **Comments:**
  > **username_0**: I applied the fix and it's working OK now, thanks again  
  > **username_1**: Excellent good to hear Andy.  
  
  ---
  
  