...and it doesn't help...I tried with 20475 and -4 in the "Max Longvarchar"
field. Text field (txt in my table) is still mapped to the Jet text type
insteed of Memo.
But mystery is going deeper...
I use Jet 4.0 on my winXP SP2. I followed the instructions describes in
the last
paragraph here :
http://support.microsoft.com/?scid=kb%3Ben-us%3B237994&x=19&y=12
...And we can read at this link :
http://support.microsoft.com/?scid=kb%3Ben-us%3B214854&x=16&y=11 that :
ODBC SQL Type:SQL_WLONGVARCHAR
Precision:N/A
Scale:N/A
Jet 3.5 Type:Unsupported
Jet 40 Type:Memo
...I still trying to find some more info about that.
Many thanks for your support.
Regards,
--
IoGuiX
Quoting Ludek Finstrle <luf@pzkagis.cz>:
>> Mh, looks impossible to join just a .exe without a part of Office pack :/
>
> It's a pity.
>
>> 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).
>
> The only difference I see is in type of 'txt' column.
> ANSI: SQL_LONGVARCHAR (-1)
> Unicode: SQL_WLONGVARCHAR (-10)
>
> Let's try change Max Longvarchar size from 8190 to something higher
> (at least 16380). If it doesn't help try change the Max Longvarchar
> size to -4 (SQL_NO_TOTAL).
>
> Maybe it helps or maybe it doesn't.
>
> Regards,
>
> Luf
>