Re: REALSQL Date fields

[Frank Bitterlich <bitterlich2@gsco.de>]

Hard to say... A binary value (6 bytes) of some sort, 07 D9 00 04 00  
11 in hex... unreadable when you assign it to a string or variant.
That might be a .Totalseconds value (or even Unix timestamp?), but I'm  
too lazy to make a trial-and-error decryption attempt...
Cheers,
   Frank+++


Am 22.04.2009 um 17:26 schrieb Aaron Bratcher:

> What does the nativeValue show?
> --
> Aaron Bratcher
>
> On Apr 20, 2009, at 11:11 AM, Frank Bitterlich wrote:
>
> > Peter,
> >
> > that might be a possible reason. However it is strange that  
> > the .StingValue representation of such a "DATE" field does _not_  
> > contain a time component. After all, that's what the TIMESTAMP type  
> > is for, at least that's what I thought :)

--

Günter Schmidt GmbH
Frank Bitterlich             eMail: bitterlich@gsco.de
Ben-Gurion-Ring 21           WWW:   http://www.gsco.de/
D-60437 Frankfurt            Tel.:  069 / 156809-29
GERMANY                      Fax:   069 / 156809-28
Geschäftsführer: Jürgen Hartwich
AG Frankfurt am Main, HRB 76504 - USt.-ID: DE235219624






_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>