Date woes

[Bart Pietercil]

Hi,

I can confirm that exact the same problem arises when the date in  
Valentina is NULL

So problem is:

when a datefield in Valentina is set to 0000-00-00 (automatically by  
inserting a record without specifying the datevalue AND field IS NOT  
nullable) or when a date is NULL the getDate VDate function returns  
an strange date (0002-11-30)--> which I suppose is the last date you  
guys had a good night sleep :-)

The problem of course remains:

what should a getDate return when I receives a NULL or 0000-00-00 ?


hth

Bart


On 26-mrt-07, at 16:47, Ruslan Zasukhin wrote:

> On 26/3/07 3:20 PM, "Bart Pietercil" <bart.pietercil at gmail.com> wrote:
>
>> Hi Ivan,
>>
>> thanks for looking into this.
>> Referring to Thorstens answer I think the problem lies in RB.
>>
>> Did you try to reproduce the problem using RB and a VDate.Getdate
>> function ?
>>
>> Probably the GetDate function does the same as what I was doing in RB
>>
>> aDate.sqldate = myCursor.Field(DateFieldName).GetString ( when the
>> DB.DateFormat is set to yyyymmdd)
>>
>> because that is giving the exact same problem.
>>
>> So it may not be an internal Valentina problem, but maybe a
>> conversion problem when the GetDate "delivers" an RB Date
>
> Yes I also think it needs check V4RB::Vdate::GetDate() method.
>
> Kirill, please check it.
>
>
> -- 
> Best regards,
>
> Ruslan Zasukhin
> VP Engineering and New Technology
> Paradigma Software, Inc
>
> Valentina - Joining Worlds of Information
> http://www.paradigmasoft.com
>
> [I feel the need: the need for speed]
>
>
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina