What if you use #dateformat(ECRTTotal.getdateentered(),"yyyymmdd")#
(just out of interest really). Somewhere in either SQL Server or even in the OS itself you could try setting your location to the US and see if that helps? On 8/06/2010 9:30 AM, Blair McKenzie wrote: The problem is probably related to dates where the day could also be interpreted as the month. From the symptoms you're describing, I would guess that yyyy-mm-dd is the default but yyyy-dd-mm is used to somehow resolve ambiguous dates.-- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en. |
- [cfaussie] Odd date behaviour - CF9/SQLServer2005 Mike Kear
- Re: [cfaussie] Odd date behaviour - CF9/SQLServ... Blair McKenzie
- Re: [cfaussie] Odd date behaviour - CF9/SQL... m...@ampersand.net.au
- Re: [cfaussie] Odd date behaviour - CF9... Peter Tilbrook
- Re: [cfaussie] Odd date behaviour -... Mike Kear
- RE: [cfaussie] Odd date behavi... Dale Fraser
- RE: [cfaussie] Odd date behavi... Steve Onnis
- Re: [cfaussie] Odd date be... Mike Kear
- RE: [cfaussie] Odd dat... Steve Onnis
- Re: [cfaussie] Odd dat... Mike Kear
- RE: [cfaussie] Odd dat... Dale Fraser
- Re: [cfaussie] Odd dat... Mike Kear
- [cfaussie] Re: Odd dat... Gavin Baumanis