I would say that the client who is using your api is not using the datetime.parse method in .net which allows you to add a "culture" specific format when a string date is parsed.
the .NET parse method is an overloaded .NET method that can either take the following forms. Parse(String) <http://msdn.microsoft.com/en-us/library/1k1skd40.aspx> Parse(String, IFormatProvider)<http://msdn.microsoft.com/en-us/library/kc8s65zs.aspx> Parse(String, IFormatProvider, DateTimeStyles)<http://msdn.microsoft.com/en-us/library/ey1cdcx8.aspx> Regards Gary Gilbert http://www.garyrgilbert.com/blog On Tue, Jan 5, 2010 at 11:14 AM, Stefan Richter <ste...@flashcomguru.com>wrote: > > My CF app stores dates in a MySQL database which I often submit simply > using NOW() in my SQL statement. The resulting database entry has this > format: > 2008-01-29 11:08:40 > Other times I am using a default MYSQL value of CURRENT_TIMESTAMP in a > timestamp field, which results in the same format. > > I have a public API which returns the date in the same format. Now one of > my clients told me this: > ".Net functions do not recognize the date/time strings that the API returns > making all date/times invalid." > > Is that really the case? Am I doing something wrong, or is he? > > Regards, > > Stefan > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:329413 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4