Privacy Policy

Guest
  • Guest
  • Guest Topic Starter
2001-12-20T05:59:25Z
Date parsed: 12/20/2001 5:59:25 AM

Date: Thu, 20 Dec 2001 12:59:25 -0600

We are using an Oracle 8i database to store the data.

We get no data in the DATETIMELOCAL or DATETIMEUTC fields (I had to change

them from DATE datatypes to VARCHAR2 datatypes to get around insert errors)

and the data we are getting in DATETIMERFC822LOCAL and DATETIMERFC822UTC

looks very odd( e.g. "Sun, 19 Jan 1659 00:38:11 -0600")

We are also logging to the supplied sample Access database and everything

looks right there.

Guest
  • Guest
  • Guest Topic Starter
2001-12-20T21:27:27Z
Date parsed: 12/20/2001 9:27:27 PM

Date: Thu, 20 Dec 2001 21:27:27 +0100

Hi,

first I must tell you that I don't have access to an Oracle DBMS, so I can't

try to reproduce your problem.

- Why did you not use the datatype 'datetime' for DATETIMELOCAL and

DATETIMEUTC ? If you do/did, what happens/ed?

- Are you using a date datatype for DATETIMERFC822LOCAL and

DATETIMERFC822UTC ? For these two fields the datatype must be 'varchar' or

'varchar2'.

Franz

"frank" <frank@mindvision.com> wrote in message

news:CifRyhYiBHA.1696@is1.netal.com...

> We are using an Oracle 8i database to store the data.

>

> We get no data in the DATETIMELOCAL or DATETIMEUTC fields (I had to change

> them from DATE datatypes to VARCHAR2 datatypes to get around insert

errors)

> and the data we are getting in DATETIMERFC822LOCAL and DATETIMERFC822UTC

> looks very odd( e.g. "Sun, 19 Jan 1659 00:38:11 -0600")

>

> We are also logging to the supplied sample Access database and everything

> looks right there.

>

>

>

Guest
  • Guest
  • Guest Topic Starter
2001-12-20T21:46:11Z
Date parsed: 12/20/2001 9:46:11 PM

Date: Thu, 20 Dec 2001 21:46:11 +0100

I just checked the MSDN and it seems that there's no 'datetime' datatype,

only a 'date' datatype that should be compatible with the 'datetime'

datatype provided by Access and MS SQL Server.

>(I had to change

> > them from DATE datatypes to VARCHAR2 datatypes to get around insert

> errors)

What kind of errors happened?

Franz

"Franz Krainer" <franzk@netal.com> wrote in message

news:Dpqr9SZiBHA.4156@is1.netal.com...

> Hi,

>

> first I must tell you that I don't have access to an Oracle DBMS, so I

can't

> try to reproduce your problem.

>

> - Why did you not use the datatype 'datetime' for DATETIMELOCAL and

> DATETIMEUTC ? If you do/did, what happens/ed?

> - Are you using a date datatype for DATETIMERFC822LOCAL and

> DATETIMERFC822UTC ? For these two fields the datatype must be 'varchar' or

> 'varchar2'.

>

> Franz

>

>

>

> "frank" <frank@mindvision.com> wrote in message

> news:CifRyhYiBHA.1696@is1.netal.com...

> > We are using an Oracle 8i database to store the data.

> >

> > We get no data in the DATETIMELOCAL or DATETIMEUTC fields (I had to

change

> > them from DATE datatypes to VARCHAR2 datatypes to get around insert

> errors)

> > and the data we are getting in DATETIMERFC822LOCAL and DATETIMERFC822UTC

> > looks very odd( e.g. "Sun, 19 Jan 1659 00:38:11 -0600")

> >

> > We are also logging to the supplied sample Access database and

everything

> > looks right there.

> >

> >

> >

>

>

Similar Topics