June 13, 2004 at 11:20 pm
i have posted one topic "serious date problem" pls answer that
<a href="http://www.websolsoftware.com"> For IT jobs click here</a>
*Sukhoi*[font="Arial Narrow"][/font]
June 13, 2004 at 11:45 pm
For some reason I couldn't reply to your other post...
I've found that inserting a date into SQL in the format yyyy/mm/dd is often best. It's unambiguous.
Maybe you can switch the order around as you do the insert
HTH
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 14, 2004 at 1:51 am
To avoid any ambiguity, I always try to enter the month as 3 letters, and show it in the same form on reports (some of which are sent to other countries) ... 04-Jun-2004 can't be misinterpreted. I'll echo a previous poster ... isdate() is good way of checking dates, and the existence of a leap year.
June 14, 2004 at 2:26 am
what iam asking you , is in which format should i enter date , to make sure that date problem doesn't occur again..
iam using ASP pages and SQL-SERVER 2000
<a href="http://www.websolsoftware.com"> For IT jobs click here</a>
*Sukhoi*[font="Arial Narrow"][/font]
June 15, 2004 at 3:34 am
use the iso standard: yyyy-mm-dd
e.g. 2004-06-15
June 15, 2004 at 3:36 am
i never knew this format is ISO Certified hehe
<a href="http://www.websolsoftware.com"> For IT jobs click here</a>
*Sukhoi*[font="Arial Narrow"][/font]
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply