On Mon, Mar 24, 2008 at 7:29 PM, Les Mizzell <[EMAIL PROTECTED]> wrote: > denstar wrote: > > Are they against letting you add a real date field? > > Seeing there's already several hundred records in the database, some > with dates, some with NONE - which is exactly what they want - adding a > real date field would be tough. It was a hard argument to start with, > and I let them win.
They won, they get to figure it out. :-) Seriously tho, when I've been in that position, I've done the following: No dates become nulls 0/0/2008 becomes 1/1/2008 12/0/2008 becomes 12/1/2008 If they want whole years spanned, months, etc. do what Sonny suggests, and add a second "end date" field. If you go with the end date, you can put whatever logic they want in there. "If only the year is specified, have it span the whole year" 0/0/2008 becomes 1/1/2008 and 12/31/2008. ditto for months: 12/0/2008 becomes 12/1/2008 and 12/31/2008. And that's logic you could add to the entry form's save routine, so future events will have "correct" dates too, without having to change the way they're inputting them now. > But - see my other email. I've had an idea while watching "House"!! > Sometimes getting out from in front of the computer is the best way to > find a solution (maybe - haven't tried it yet)!! Oh yeah. Breaks are good for the noggin, and water doesn't hurt either. :-) -denny -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;160198600;22374440;w Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:302056 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
