Re: Access97/odbcUnicode/pgsql : unable to map text field

From: JGuillaume 'IoGuiX' de Rorthais <igxnews(at)free(dot)fr>
To: Ludek Finstrle <luf(at)pzkagis(dot)cz>
Cc: pgsql-odbc(at)postgresql(dot)org
Subject: Re: Access97/odbcUnicode/pgsql : unable to map text field
Date: 2006-06-09 12:53:17
Message-ID: 20060609145317.1xc09lynswwcoowo@imp4.free.fr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

Mh, looks impossible to join just a .exe without a part of Office pack :/
I just have my logs for you...

Anyway, indeed, mapping PgSQL Text type to Access Memo work fine with
the ANSI's
ODBC versions. But using the ANSI version require to much macro & VBA stuff to
workaround the #Deleted behaviour (that is an Access specific problem).

So, I resume :
- with Ansi version, I have to play with VBA & macro code because of
Access BUT
Text -> Memo type work fine ;
- with unicode version, Text -> Memo type is broken BUT I havn't the #Deleted
problem...

I put my log from ansi driver by inocchichichi here :
http://ioguix.free.fr/psqlodbc_ansi.log
http://ioguix.free.fr/mylog_ansi.log

Thanks for your help !

--
JGuillaume 'IoGuiX' de Rorthais

Quoting Ludek Finstrle <luf(at)pzkagis(dot)cz>:

>> Thanks, it's good to have some support...It's so long I am looking for some
>> workaround about bugs with odbc unicode or Access (w/ odbc ansi)...
>
> I don't know what Access needs to recognize the data as MEMO. Has someone
> an idea?
> I have no Access installed on my computer. Please could you send
> me sample .exe and data which reproduces the problem?
>
> Regards,
>
> Luf
>

In response to

Responses

Browse pgsql-odbc by date

  From Date Subject
Next Message Ludek Finstrle 2006-06-09 13:50:30 Re: Access97/odbcUnicode/pgsql : unable to map text field
Previous Message Ludek Finstrle 2006-06-09 12:42:43 Re: Patch for snprintf problem (bug #1000650)