Timestamp type hangs my .dll

[TheKing]

I am using a vb6.0 .dll to connect to an oracle 9i database.

I have just found out that my msProvider doesn't recognize the 'timestamp' field type.
If I use the data provider provided by oracle 9i everything works. but I am locked into the ms provider.
Now this works in .net but I have to use this 6.0 .dll for this web application.

I was wondering (and I haven't been able to find anything yet) if there might be a patch for the ms provider for oracle that would fix my oracle 9i problem.

Thanks alot


T^he_Kiⁿg

 

[chiph]

I don't know why you're locked into the MS provider -- it doesn't connect to Oracle itself directly anyway -- you still need the Oracle client libraries installed to provide the OCI layer. The MS layer just slows things down.

I would push for using the Oracle provider, or switch to someone like DataDirect (they are at

http://www.datadirect-technologies.com/).

Chip H.

 

[TheKing]

Well that is not an option here, the 'client' is writting the front end in VS.NET and I am writting the backend dll in VB6.0. They will only use the ms oracle provider.

My problem really is this new 'timestamp' field type in Oracle 9i. Man it seems to be a bugger.



T^he_Kiⁿg

 

[chiph]

If this datatype is new to Oracle 9i, you've got a problem -- because the MS OLEDB provider is fairly old, and probably was written before 8i came out, much less 9i.

The other thing to remember is that in .NET, the providers are part of the .NET framework (or a separate download, in the case of the ODBC and managed Oracle provider) (Note: these are now included in v1.1 of the framework). So they aren't going to be using the same provider as you in any case. But because they're talking to Oracle, both of you will need the Oracle client software on your PCs - you'll be using the COM-based OLEDB provider, and they will be using the Oracle ADO.NET provider.

Chip H.

 

[TheKing]

Well I got it figured out.
I am using the Oracle 9i provider
They are using the .NET provider for Oracle 9i.
Both seem to be able to coexist for now.

Also I need this in my select statement in order to read a 'timestamp' field type.

SELECT to_date(to_char(field_name, 'mmddyyyy hh24:mi'),'mmddyyyy HH:mi') field_name FROM Table_name

That code now works for me, I can read in a timestamp field type now.

Thanks


T^he_Kiⁿg