Access97/odbcUnicode/pgsql : unable to map text field to memo type

Hello,

I use odbc unicode driver to link tables from my pgsql 8.1.3 server to
Access97 SR2 (and latest jet engine 4.0 SP 8).

Everything is working well, even inserting row work without #deleted on
update (like with the ansi driver despite of serial PK on tables :s)

Actualy, one thing doesn't work properly. It's a well know issue, but I
didn't find how to correct it (_and_I_read_lots_of_webpages_about_that_!_)

TEXT type in my pgsql database aren't map to memo type in Access. I
don't mind sorting, index or order on these fields, but I really need
more than 255 chars on them.

And, yes, checked the "text as LongVarChar" in the ODBC configuration.

Here the table I use for my tests :

CREATE TABLE test
(
id serial NOT NULL,
txt text NOT NULL DEFAULT ''::text,
CONSTRAINT test_pkey PRIMARY KEY (id)
)
WITH OIDS;

I think you will find the complete ODBC configuration in the HUGE logs
here : http://ioguix.free.fr/pgsqllog.log

Please....help... (or point me in the right direction)

Thanks
--
+-----------------+
| IoGuiX |
| igxnews@free.fr |
+-----------------+

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Re: Access97/odbcUnicode/pgsql : unable to map text fieldto memo type

This is a multi-part message in MIME format.
--------------090004000001000205040006
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Its an Access problem.
I made linked tables to a postgresql 8.x database (on Linux server) with Access 97 and Access XP.
Access 97 interpreted the Postgresql text type column as Access Text(255) (That's Bad).
Access XP interpreted the same as Memo (That is Good).

I don't know if any of the ODBC driver settings can overcome the issue.



ioguix wrote:
> Hello,
>
> I use odbc unicode driver to link tables from my pgsql 8.1.3 server to
> Access97 SR2 (and latest jet engine 4.0 SP 8).
>
> Everything is working well, even inserting row work without #deleted on
> update (like with the ansi driver despite of serial PK on tables :s)
>
> Actualy, one thing doesn't work properly. It's a well know issue, but I
> didn't find how to correct it (_and_I_read_lots_of_webpages_about_that_!_)
>
> TEXT type in my pgsql database aren't map to memo type in Access. I
> don't mind sorting, index or order on these fields, but I really need
> more than 255 chars on them.
>
> And, yes, checked the "text as LongVarChar" in the ODBC configuration.
>
> Here the table I use for my tests :
>
> CREATE TABLE test
> (
> id serial NOT NULL,
> txt text NOT NULL DEFAULT ''::text,
> CONSTRAINT test_pkey PRIMARY KEY (id)
> )
> WITH OIDS;
>
> I think you will find the complete ODBC configuration in the HUGE logs
> here : http://ioguix.free.fr/pgsqllog.log
>
> Please....help... (or point me in the right direction)
>
> Thanks

--------------090004000001000205040006
Content-Type: text/x-vcard; charset=utf-8;
name="greg.campbell.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="greg.campbell.vcf"

begin:vcard
fn:Greg Campbell
n:Campbell;Greg
org:Michelin North America - US5 Lexington;ENG-ASE
email;internet:greg.campbell@us.michelin.com
title:ASE Systems Engineer
tel;work:803-951-5561/x75561
x-mozilla-html:FALSE
version:2.1
end:vcard


--------------090004000001000205040006
Content-Type: text/plain
Content-Disposition: inline
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

--------------090004000001000205040006--