From: | Benjamin Scherrey <scherrey(at)proteus-tech(dot)com> |
---|---|
To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: BUG in Unicode Driver - was: Re: Can't get more than 255 |
Date: | 2002-12-01 17:31:44 |
Message-ID: | 200212011231.44922.scherrey@proteus-tech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
:-( Thanx for looking into this Hiroshi. Its odd that the only Unicode
problem that Access 97 would have is not being able to tell that a
text field is a memo field - because everything else seems to work
fine. Regardless - is there anyway we can figure out why, when
displaying the table data, the non-Unicode driver ends up with a
bunch of 'Name?' strings rather than the data? If either of these
problems was corrected I'd be able to deliver this project. As it is
- upgrading them to a new version of Access is the last thing they
(or I) want to do.
best regards,
Ben Scherrey
On Sunday 01 December 2002 08:06 am, Hiroshi Inoue wrote:
> I got Mylog output from Benjamin and examined it. Certainly he
> turns on *Text As LongVarChar* option and the log seems to be
> almost the same as the one I get here using Access 2000.
> Maybe the difference comes from the difference of Access version.
> Unfortunately Access 97 doesn't seem to understand UNICODE.
>
> regards,
> Hiroshi Inoue
From | Date | Subject | |
---|---|---|---|
Next Message | Ben Trewern | 2002-12-01 22:00:10 | ODBC, Numeric and Access |
Previous Message | Hiroshi Inoue | 2002-12-01 13:06:09 | Re: BUG in Unicode Driver - was: Re: Can't get more than 255 |