>In my opinion, in most situations, the best way is not to do it from CF at >all. Simply define the default value within the database column. That way, >if you write future applications in other environments that use the same >database, they'll function identically.
Got it, Dave. Part of my problem was that I was not specifying the field names in my insert statement, thus it was trying to force a value into a field that was set to have a default value. I have not explicitly stated by values and destination fields (leaving the date out) and all is well. Man, the further away from Access I get, the worse it becomes... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:267658 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
