That's why I wrote "betterdate" back in the 4.7 days. I meant to turn this into a patch for 5, but it just slipped my mind. I guess I have no excuse for 6. http://drupal.org/project/betterdate -M ---------- Forwarded message ---------- From: Syscrusher <syscrusher@4th.com> Date: Mar 30, 2007 10:16 PM Subject: [development] One other teensy FAPI question To: development@drupal.org Using the 'date' field type, how does one cause the field to allow a "not specified" date? Is this not supported? I want to use dates in a search form as an optional parameter, not a required one. Right now I am detecting a "null" date by looking for 1900-01-01, but in this particular application (a genealogy research module), that happens to be a perfectly legitimate value. Probably nobody else has needed this yet, and it isn't supported, but I thought it didn't hurt to ask. At worst case, I may have to just reserve that value. I don't want to burden the user with a checkbox for each of the *four* available date search parameters. Scott -- ------------------------------------------------------------------------------- Syscrusher (Scott Courtney) Drupal page: http://drupal.org/user/9184 syscrusher at 4th dot com Home page: http://4th.com/