Received: from platinumsolutions.com (dns-1.tricreations.com [216.205.16.110]) by hub.org (8.10.1/8.10.1) with SMTP id e5JJOKM00369 for ; Mon, 19 Jun 2000 15:24:20 -0400 (EDT) Received: from rsdevelop ([24.28.194.228]) by platinumsolutions.com ; Mon, 19 Jun 2000 15:16:40 -0400 Message-ID: <002801bfda24$4f2d2620$0200a8c0@RSGROUP> Reply-To: "Adam Rossi" From: "Adam Rossi" To: Subject: Simple Q: Does the ODBC driver support LONGVARCHAR? Date: Mon, 19 Jun 2000 15:26:39 -0400 Organization: PlatinumSolutions Inc. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Archive-Number: 200006/79 Does the ODBC driver support longvarchar? It seems that no matter what I do with the settings for the driver, such as checking "Unknowns as LongVarChar", "Text as LongVarChar", "Parse Statements", etc., the longvarchar type NEVER works. In this simple SQL statement: create table test_table testid INTEGER, text_field LONGVARCHAR, var_field VARCHAR(250), char_field CHAR(1)) the field "text_field" defined as type "LONGVARCHAR" will always cause the statement to fail with the following message: ERROR: Unable to locate type name 'longvarchar' in catalog' (#17) If I change the "LONGVARCHAR" to "TEXT", the statement below works fine: create table test_table testid INTEGER, text_field TEXT, var_field VARCHAR(250), char_field CHAR(1)) Since I am relying on some builder tools that only support ODBC standard types (i.e. LONGVARCHAR and not TEXT), it would make my life a lot easier if I could get LONGVARCHAR to work. Is this some deficiency in the driver? Shouldn't an ODBC driver support the major ODBC types? Could anyone point me in the right direction to hack the driver if it currently does not support this syntax? Thanks for your help. - Adam