One of the things we're having a hard time with is the "date" field type. I find the "3 field" approach to be cumbersom for data entry. Is there a better way? I love the flexibility that dabbledb offers in this regard and would love to see that functionality incorporated.
Thanks!
J
Comments
With our date or date and time fields you will see a calendar to select a data when using the "click to change" option on a view displayed in the table format. When editing a single record you recieve a link to set the current date but the calendar is not yet available in this area. What sort of flexibility are you after?
Well...we do a lot of data entry, and the dates come in all types of formats. I'd like to be able to just type in the date in any number of formats and have it translate into the "TrackVia date format" i.e. entering 2005.12.31, 12/31/05, 31 Dec 05, or December 13th 2005 would all be recognized as valid dates. Right now when we're entering dates you have to translate from the numerical month to the abreviated month and in a certain order. Also, when typing in the year, it defaults to 1990 or something which is problematic for birthdays. We have to tab into the year field, type "m" for "more", and then type out the whole year. I know these issues aren't huge, but they make a big difference when doing data entry. We actually considered using a text field instead for these reasons.
We've logged this request as a suggested enhancement to our date fields.
Thanks