Martin has informed me that Microsoft doesn't support SQLDescribeParam and
in the absence of an explicit bind_param, miscasts the data as VARCHAR.
$sth->bind_param(1, undef, SQL_LONGVARBINARY);
Solved the problem.
--- Begin Message ---
On 28/01/16 15:08, Jerrad Pierce wrote:
Hello Martin,
$DBI::VERSION = 1.634
$DBD::ODBC::VERSION = 1.52
It would also be useful to know the column type in your access DB.
I'm updating a LONGBINARY column in a Jet 4 (MDB) database.
Thanks
Thank you
I forgot, MS Acces
On 27/01/16 22:10, Jerrad Pierce wrote:
Hello all, I'm updating a LONGBINARY column in a Jet 4 (MDB) database on
Windows 7 with
DBD::ODBC and have encountered an odd issue. Rather than the common problem of
Unicode
data being treated as bytes, I have bytes that seem to be being treated as
UCS-
Hello all, I'm updating a LONGBINARY column in a Jet 4 (MDB) database on
Windows 7 with
DBD::ODBC and have encountered an odd issue. Rather than the common
problem of Unicode
data being treated as bytes, I have bytes that seem to be being treated
as UCS-2LE.
Data that should look like this in
I have the problem whether I use the default DBD::ODBC from Strawberry Perl,
or one built specifically with Unicode disabled.
DBI::db=HASH(0x25f2608) trace level set to 0x6000100/2 (DBI @
0x0/0) in DBI1.634-ithread (pid 1844)
-> prepare for DBD::ODBC::db (DBI::db=HASH(0x25f26e0)~0x25f260
