I forgot to mention that CreateODBCDateTime(now()) doesn't do the
trick either. Just tried your idea and got this:
The cause of this output exception was that:
coldfusion.runtime.locale.CFLocaleDateFormatException: "{d
''2006-12-31''}" is an invalid date format.
I have found a solution but it makes ZERO sense: Give up on
cfqueryparam and do a raw insertion. If I do that the db will accept
both #now()# and #CreateODBCDateTime(now())# with similarly corrrect
results in a Sql Server datetime field.
Which points to cfqueryparam, which in turn points to java/jdbc? How
can this happen? While its not the end of the world to do without
cfqueryparam in this instance, I really don't like to 'go bare' like
this. Especially for something so apparently bizarre.
--
[EMAIL PROTECTED]
Janitor, The Robertson Team
mysecretbase.com
On 12/31/06, Claude Schneegans <[EMAIL PROTECTED]> wrote:
> How about
>
> <cfqueryparam value="#createODBCDate(now())#" cfsqltype="CF_SQL_DATE">
>
> --
> _______________________________________
> REUSE CODE! Use custom tags;
> See http://www.contentbox.com/claude/customtags/tagstore.cfm
> (Please send any spam to this address: [EMAIL PROTECTED])
> Thanks.
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Create robust enterprise, web RIAs.
Upgrade & integrate Adobe Coldfusion MX7 with Flex 2
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:265437
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
