Received: from platinumsolutions.com (dns-2.tricreations.com [216.205.16.111])
	by hub.org (8.10.1/8.10.1) with SMTP id e5GIRLM78638
	for <pgsql-interfaces@postgresql.org>;
	Fri, 16 Jun 2000 14:27:21 -0400 (EDT)
Received: from rsdevelop ([24.28.194.228]) by platinumsolutions.com ;
	Fri, 16 Jun 2000 14:22:03 -0400
Message-ID: <06ae01bfd7c0$e97b7c60$0200a8c0@RSGROUP>
Reply-To: "Adam Rossi" <adam.rossi@platinumsolutions.com>
From: "Adam Rossi" <adam.rossi@platinumsolutions.com>
To: <pgsql-interfaces@postgresql.org>
Subject: ODBC longvarchar error - why does this not work?
Date: Fri, 16 Jun 2000 14:30:13 -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/75

I am trying to use Visio enterprise in conjunction with PostgreSQL 7.0.2 via
the ODBC driver (6.5). It works perfectly except for one small issue -
longvarchar types do not work. I have searched the archives and tried a
number of different ODBC driver settings (unknown as LONGVARCHAR, TEXT as
LONGVACHAR, PARSE STATEMENTS, etc) with no success. The relevant portion of
the ODBC log is included below. As you can see, I have two fields defined as
LONGVARCHAR. Tables without longvarchar fields are created without any
errors.

conn=131151048, query='BEGIN'
conn=131151048, query='create table practice (    practice_id INTEGER not
null,   practice_des LONGVARCHAR,   practice_inst LONGVARCHAR,   pop_up_def
VARCHAR(250), constraint practice_pk primary key (practice_id) )    '
ERROR from backend during send_query: 'ERROR:  Unable to locate type name
'longvarchar' in catalog'

Thanks for your help.

- Adam