Data type for parameter 4 has changed since first SQLExecute call.
I think this isn't really a DBI issue, but rather a driver specific (mis)feature...
You could try WorkArounds=536870912 (no, not kidding :) — or, as I dimly recall 'WorkArounds' not being applicable with the wire protocol driver (see the readme), try the other suggestion (SQLFreeStmt) made in the thread I linked to. Good luck!
In reply to Re: DBI: data types, binding and insertions
by almut
in thread DBI: data types, binding and insertions
by Sandy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |