Author: geoffHome | Posted on: 9/4/2009 7:53:26 PM | Views : 355

My most common problem is always related to dates being incompatible across 'platforms'.  I'd really like to know what is the most appropriate way to deal with dates to cure this once and for all.
Example:  In Australia we traditionally select dates as dd/mm/yy and all is OK while I continue development on my PC with my resident asp.NET and SQL Server.
However upon deployment to a US Server the problems start (defaults to mm/dd/yy I assume).  Nothing is obvious until a date like 13th September is used and data is being updated on the US SQL Server
What should I set to overcome this issue that catches me constantly?
Thanks,
Geoff
...

Go to the complete details ...