Skip site navigation (1) Skip section navigation (2)

Re: MS Access problem with memos

From: Jeff Eckermann <jeff_eckermann(at)yahoo(dot)com>
To: postgresql(at)innysoft(dot)com, pgsql-odbc(at)postgresql(dot)org
Subject: Re: MS Access problem with memos
Date: 2005-01-10 21:00:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-odbc
--- Zanoni Marco <postgresql(at)innysoft(dot)com> wrote:

> Hi,
> I have a problem with the ODBC driver and MS Access
> XP.
> If I have a table on PostgreSQL ( version 7.4.6)
> with text column,
> MS Access reads it as a varchar(254) column, instead
> of a "Memo" dataytpe.
> The official doccumentation says that the driver
> option "Text as
> LongVarchar" should map text as memos, but it
> doesn't work.

Works for me.  Did you remember to relink the table(s)
after you made that change?  (The Linked Table Manager
might be enough).

> I read an old workaround to make this work, but it
> says to create a new type,
> and since 7.4 it must be coded in C. Is it the only
> way?
> I work on Windows 2000, the latest official version
> of the driver, and
> PostgreSQL 7.4.6 on Gentoo Linux.
> Do anyone know why it doesn't work?
> Thanks for your help.
> Regards,
> Zanoni Marco
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose
> an index scan if your
>       joining column's datatypes do not match

Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 

In response to


pgsql-odbc by date

Next:From: LucianoDate: 2005-01-10 22:10:36
Subject: Query with hexadecimal characters
Previous:From: Zanoni MarcoDate: 2005-01-10 17:29:06
Subject: MS Access problem with memos

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group