Hi Alexander, I found the same problem when I moved from 6.5 to 2000.
In SQL 2000, new Inserts with fields with a SMALLDATETIME type wasn't storing the seconds, so subsequent Searches based on a <@CURRENTTIMESTAMP> variable returned improperly. In my SQL 2000 databases I converted all my fields with a SMALLDATETIME datatype to DATETIME. Cheers... Scott Cadillac http://xml-extra.net [EMAIL PROTECTED] VP, Research and Development Plus International Corp. 604-460-1843 [EMAIL PROTECTED] http://www.plusinternational.com Vancouver, BC, Canada Does your company have an Enterprise Information Portal? Check out Salsa at www.plusinternational.com/flash/salsa.htm ----- Original Message ----- From: "Alexander Zatko" <[EMAIL PROTECTED]> To: "Multiple recipients of list witango-talk" <[EMAIL PROTECTED]> Sent: Wednesday, May 22, 2002 8:06 AM Subject: Witango-Talk: date format and SQL 2000 > Trying to migrate my DB from MS SQL 6.5 to 2000 and have a problem with > dates. > > In my taf I define local var where I store <@CURRENTTIMESTAMP> > > I use this variable to insert value into a smalltimestamp type column (let's > call that column STAMP) > > Immediately after that I am searching for that record WHERE STAMP is the > value of variable defined in the beginning. > > However, the search fails and I noticed that: > > 1)the format of the variable value is 05/22/2002 10:48:16 > 2) Tango changes this format to {ts '2002-05-22 10:48:16'}, but it changes > it for both - the insert, as well as the search actions. > > Anybody has any ideas how to deal with this? > > Thanks > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
