RE: ODBC Error

From: "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>
To: "'gary(dot)wolfe(at)lsbc(dot)com'" <gary(dot)wolfe(at)lsbc(dot)com>, pgsql-odbc(at)postgresql(dot)org
Subject: RE: ODBC Error
Date: 2001-08-24 08:11:07
Message-ID: E2870D8CE1CCD311BAF50008C71EDE8E01F74688@MAIL_EXCHANGE
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Is that MS Access 97? I've found a similar problem with text fields.
I *think* it might be that M$ Access '97can't index Memo fields in its own
tables so doesn't believe tables can have memo fields indexed. Maybe turning
of Unique index recognition might work? I'm using Access 2000 now and that
doesn't seem to suffer that problem (just a whole host of new and
interesting, er, features :) )
I've never used SAS so don't what it is based on, but maybe if it
utilises Jet 3.5 it could suffer from a similar problem?
- Stuart

> -----Original Message-----
> From: Gershon M. Wolfe [SMTP:gary(dot)wolfe(at)lsbc(dot)com]
> Sent: Thursday, August 23, 2001 1:35 AM
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: ODBC Error
>
> Dear ODBC users,
>
> When trying to import a table into MS Access or SAS, I get the
> following
> error:
> "Invalid field definition 'session' in definition of index or
> relationship".
> This error only occurs when a text field called "session" in the table
> is indexed. Here is how I index the field:
>
> create index report_session on report using btree (session text_ops);
>
> When I drop the index there is no longer an error.
>
> Gary
>

Browse pgsql-odbc by date

  From Date Subject
Next Message Henshall, Stuart - WCP 2001-08-24 08:15:38 RE: I cant' configure ODBC
Previous Message Hiroshi Inoue 2001-08-24 06:59:54 Re: Error messages not always reported through the ODBC driver -STATEMENT ERROR missing