I have done some additiona investigate into this problem and found the
following:
As described below the problem does not begin to appear until the return
value size is > 2048.
Once the return value is greater than 2048 bytes the value returned by
pyodbc is 2 times the actual size of the retur
Thank you for your response but this is not an Access problem.
The exact same code using mx.ODBC or using the old odbc.py that comes with
the win32 files works fine.
It only fails with pyodbc.
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> On May 18, 6:46 pm, "Joe Salmeri" <[EMA
On May 18, 6:46 pm, "Joe Salmeri" <[EMAIL PROTECTED]> wrote:
> I have found a data corruption problem with pyodbc.
>
> OS = Windows XP SP2
> DB = Microsoft Access XP
>
> PROBLEM:
>
> When selecting columns from a table that are of type Memo the value
> returned is padded with a bunch of null charac
I have found a data corruption problem with pyodbc.
OS = Windows XP SP2
DB = Microsoft Access XP
PROBLEM:
When selecting columns from a table that are of type Memo the value
returned is padded with a bunch of null characters at the end.
The problems does not seem to occur until the length of th
