I definitely want to add my vote to the requirement for a DATE format on custom fields in the database. I recently implemented Wild Apricot for the Australian Register of Homoeopaths and they are very dependent on certain dates. Their registrants need to have up-to-date insurance and 1st aid certificates to be able to gain rebates for their clients from private health funds. So they need the ability to filter for date ranges so that they can send out timely reminders. This is totally impossible at the moment.
As an extension to this requirement, having an 'alarm' facility that functions similar to the membership renewal and could be switched on against selected date fields, with flags that pop up and optional automated (but editable) email messages sent to the member and/or administrator, would be brilliant.
Another issue around date fields at the moment is the format they present in. Having the time stamp as well as the date displayed on fields that have been uploaded from date fields out of Excel is annoying as it clutters up the field and makes it quite unreadable.
Also, the upload process of date fields is not very robust. Even when setting the date format in Organisation Details settings, uploaded dates do not behave accordingly. Recently I had to perform three uploads fo the same fields because when uploaded as TEXT fields with slashes (/) the fields in Wild Apricot would reset themselves to dates and change the uploaded values from DD/MM/YYYY to MM/DD/YYYY plus time stamp which is not a used format in Australia. When I tried the format DD-MMM-YY, they reset themselves to YYYY-MM-DD, again with time stamp. Finally I gave up and used DD.MM.YYYY to have a pure text field. However, this format does not suit the purpose very well.
I am aware that you are very busy but I agree with some comments that DATE fields are something very fundamental and their unavailability takes a way from a great product!
Best regards,
Vera Externest