asked on

ADO/Oracle/ODBC 2000 Character Cutoff?

I've got an Oracle8 database with a column that is a Varchar2(4000). When I move data into this column and save it, a null is being inserted at position 2001. I was forced to convert this column to a LONG to avoid this, but I'd rather not because I can't sort and the like on it now.

What's with this 2000 limit? Is it ADO, ASP, ODBC, or Oracle? ? Help!

Thanks!

Mark Franz

Oracle has a 2Mb limit on varChar() fields so it's not Oracle, what version of MDAC are you using?

Mark Franz

Sorry, bad data... the 2Mb is really 2Gb and it is for a Long() datatype, the 2k cutoff you are experiencing ~could be that the type is not being recognized and it's being interpreted as Char().

jablan

ASKER

Let me clarify:

Column was type VARCHAR2(4000).

When I inserted data into the column via ASP/ADO (Microsoft Oracle Driver latest version), it inserts a null char at position 2001.

I don't think it's Oracle, I think it's ASP/ADO/ODBC...

Mark Franz

Yeah... thats why I asked what version of MDAC you had loaded?

Mark

jablan

ASKER

it's the 4202.3 version. The latest according to the MS site. I just checked.

Mark Franz

The OLEDB for Oracle should look like this;
MSDAORA.DLL 02.10.3711.0 Microsoft OLE DB Provider for Oracle

edwardpoon

But it seems that the ODBC provided by Microsoft doesn't work well. Have you download the ODBC driver from the Oracle Homepage?

I am using Oracle 8i Server, I have downloaded the ODBC driver from the Oracle Homepage, it works well and your problem doesn't exist.

jablan

ASKER

I've had problems with Oracle's ODBC driver. Specifically when it comes to public synonyms. It used to not recognize them. I'll give it a try.

ASKER CERTIFIED SOLUTION

Mark Franz

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

jablan

ASKER

Thanks for the info. We're using ODBC, not the OLE DB stuff. I'm not sure how to switch that over.

Mark Franz

I don't use OLE either, strictly ODBC or ADO.