Re: Date Problem with OLEDB

BTW, i'm using oracle 8.1.7...

"Bill Hunt" <huntbill_at_yahoo.com> wrote in message news:4vT59.140818$D8.5072739_at_news4.srv.hcvlny.cv.net...
> Hello,
> I have a table that has a field called date_scan. It is set up to
> default to : TRUNC(SYSDATE). All inserts to this table are done through a
> stored procedure in a a package. I ommit date_scan from the insert
> statement so it defaults to SYSDATE. I am using VB6 with ado 2.7. When i
> execute the stored procedure connected to the db using MSDAORA provider
> everything works great and the date_scan field gets a value of "8/12/2002"
> if i run the exact same code connecting using the oracle oledb provider
> OraOLEDB.Oracle the date field gets populated incorrectly. It gets a
 value
> of "8/20/0012 2:00:00 AM". Any ideas what would cause this problem, i
 need
> to use the oracle provider because I am working with blobs. This is
 driving
> me crazy...My connection strings look like this :
>
> gCon.ConnectionString = "Provider=OraOLEDB.Oracle;PLSQLRSet=1;Data
> Source=ORASERVER;User ID=xxxx; Password=xxx;"
>
> gCon.ConnectionString = "Provider=MSDAORA;PLSQLRSet=1;Data
> Source=ORASERVER;User ID=xxx; Password=xxx;"
>
> Thanks,
> Bill
>
>
Received on Mon Aug 12 2002 - 21:48:42 CEST