Re: CLOB has me wishing for a new MDAC release




<fostermark@xxxxxxxxx> wrote in message
news:41a332ea-0bf8-4cba-b03d-f83450a951b9@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
If I've done my Googling correctly, the Microsoft OLE DB driver
included in MDAC 2.8 was developed against Oracle 7.1. This means
that anything specific to the last 3 major versions of Oracle is not
supported by MSDAORA. Therefore, while Oralce has deprecated the Long
and Long Raw datatypes, I am forced to alter the CLOB columns in our
9i database to Long if I want to use MSDAORA.

One of my hands is tied by the fact that I'm using Crystal Reports to
read from the column in question. This means I can't write any
chunking code into my data access layer. The other is tied by the
fact that OraOLEDB.Oracle doesn't seem to work on the client's
server. They claim to have the appropriate Oracle client tools
installed, but the reports throw errors if any provider other than
MSDAORA is specified at design time.

So, what kind of trouble am I gong to encounter down the road if I
alter these CLOBs to Longs? Do I have any other alternatives?

Thanks much...

Unsatisfactory reply follows.

I would work on trying to help them discover why they can't use the Oracle
supplied OLE DB providers with Crystal Reports. Until then you can cobble
the CLOBs to Longs - but I think you're going to have 'trouble' of some kind
any way. That provider is just plain out of date.

If you have a thick wallet you might investigate DataDirect providers. They
are very robust and come with good support.
http://www.datadirect.com/products/ado/index.ssp

-ralph


.



Relevant Pages

  • Re: ORACLE CLIENT USERS BEWARE: Bug in Query Builder breaks SQL
    ... Comparing the Microsoft .NET Framework 1.1 Data Provider for Oracle ... When trying to use the Query Builder with Oracle, ...
    (microsoft.public.vsnet.general)
  • Re: Oracle Database Access via IIS 6.0 ASP Pages on Windows 2003 S
    ... >Oracle 10g Client is installed on the Windows Server. ... >This is my standard DSN Less connection. ... >Microsoft OLE DB Provider for ODBC Drivers error '80004005' ...
    (microsoft.public.inetserver.iis)
  • Re: Cant get Oracle OLE DB provider to work from SSIS on a 64-bit environment
    ... The project I'm trying to get running, consists of approx 25 seperate packages where 3-4 of them gets data from different Oracle sources, but I'm not even got to the point where I'm trying to run the whole lot. ... There are two issues in the topic that could be an issue, and that is to switch the whole project to 32-bit mode and then the part that says that the Designer only shows 32-bit versions of the provider. ... What I think I'll try now, it to install the 32-bit version of the Oracle ODAC to see if that makes any difference. ... uninstall ODAC and when I uninstall the regular Oracle Client with the ...
    (microsoft.public.sqlserver.dts)
  • Re: ORA-1866 The datetime class is invalid error...the saga continues!
    ... but you could try using a different data provider. ... Use the Microsoft ADO.NET Oracle Provider ... VB.NET to my employers and not being able to query data using a date field ... SQL statements I provided earlier will execute flawlessly in any enviornment ...
    (microsoft.public.dotnet.general)
  • Re: Accessing Oracle 9i tables on a Linux box
    ... MSFT and Oracle more or less universally abandoned the common interface, ... developing interfaces that take best advantage of the specific provider. ... ADO/OLEDB as was the last universal interface, ... we are primarily an Oracle shop here, and have been for many years, but we ...
    (microsoft.public.dotnet.framework.adonet)