> -----Original Message-----
> From: Hiroshi Inoue
> Benjamin Scherrey wrote:
> > 11/27/2002 8:48:29 PM, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> wrote:
> > >Hmm strange.
> > >Here, if I turn on the *Text As LongVarChar* DSN option
> > >I see a memo field and if I turn off the option I see
> > >a text field.
> > >Do you relink the table after you changed DSN options ?
> > >
> > Yeah - I redo everything from scratch each time to ensure
> > that its a fresh connection. Are
> > you using the Unicode driver when this happens for you?
> > FWIW - we've still got Access 97 here
> > but it recognizes memo fields correctly with the other two drivers.
> > What version of Access are you running?
> I'm using Access 2000 here.
> OK could you send me the Mylog debug output ?
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.
In response to
pgsql-odbc by date
|Next:||From: Benjamin Scherrey||Date: 2002-12-01 17:31:44|
|Subject: Re: BUG in Unicode Driver - was: Re: Can't get more than 255|
|Previous:||From: Joel Burton||Date: 2002-11-30 20:57:58|
|Subject: Re: Can't get more than 255 chars out of memo field in Acc|