I'm stuck on this one, and hope someone out there can tell me where to look
for answers. Here's the scenario:
On the PC side, I'm running NT4, SP4 using DB2 Connect (version 5.2, I
think) to hook via ODBC to a VM host.
On the VM side, I'm running DB2 version 5.2, and I have a table that looks
When I link this table to an Access 97 database, the last field shows as a
Memo field. Until this morning, I had no problems updating any of these
fields. In fact, the Access application was the mechanism used to update the
Anyhow, this morning, I went to update the message, and got an ODBC error
416. I then got further information from ODBC as such:
"[IBM][CLI Driver] CLI0150E Driver not capable. SQLSTATE=S1C00 (#-99999)"
I can update any other field in the table with no problems. Further, from
the VM side, I can update SY_MESSAGE easily. The stopgap method I've used is
to redefine SY_MESSAGE as a CHAR(254) field, which gets me over the hump for
My question, then, is this: Can anyone tell me, based on this message, what
piece of my software may be broken? My client's help desk is not the best,
and before I try to get the real problem fixed, I'd like to have some idea
where to turn!
6. VB puzzlers