Date woes

[Ivan Smahin]

Hello Bart,

Monday, March 26, 2007, 2:51:45 PM, you wrote:

BP> Hi,


BP> in a table I have (among other fields) 2 datefields

BP> datefield1  is set to a valid sqldate when inserting a new record
BP> datefield2 is not touched and presumably defaults automatically  
BP> 0000-00-00

BP> The db is set to yyyymmdd

BP> So far everything is as expected

BP> However when I start retrieving values then this code gives  
BP> unexpected results:

BP>          case EVFieldType.kTypeDate

BP>            DateString = mCursor.Field(i).GetString ---> 0000-00-00
BP>            aDate = mCursor.DateField(i).GetDate()--->0002-11-30

BP> aDate is now 30/11/02

BP> Why ?

BP> I mean where does that value come from and how can I make the  
BP> distinction whether the date value is legitimate or the datevalue is  
BP> not a valid date ?

Could  you  send  me  some  little  test  project  -  just I could not
reproduce it.

-- 
Best regards,
Ivan Smahin 
Senior Software Engineer
Paradigma Software, Inc
Valentina - The Ultra-Fast Database
http://www.valentina-db.com