Jeff,

Thanks for the work around.  The test script wid/id problem was a cut and 
paste error.  I have added the $dbh->{odbc_default_bind_type} = 
DBI::SQL_VARCHAR to my code for now and it is working fine with 0.40.

As for the actual problem, you feel that it is a problem with the MS SQL 
ODBC driver itself?

Dale

>From: "Jeff Urlwin" <[EMAIL PROTECTED]>
>To: "Dale Couch" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
>CC: <[EMAIL PROTECTED]>
>Subject: RE: :ODBC, Datetime strings and placeholders
>Date: Mon, 15 Apr 2002 12:36:55 -0400
>
>Dale --  Ok --
>
>I'm using a "fixed" version of DBI 1.21 (which shouldn't affect the issues,
>but just in case, I thought I'd let you know.  The preparse stuff had a
>problem that was failing the tests and crashing.  I'm not seeing that
>behavior here).
>
>I tried with the older version and the newer version and you are right .. I
>see the same problem(s).
>
>I did find one problem in your script, where you are looking for the column
>'wid', instead of ID.  Minor, but that might account for the uninitialized
>value warning.  It might also be a result of setting up the test... so, it
>may not be the problem either...
>
>Now for the meat of the issue.  I can get around the problem by using
>bind_param(1, $uValue, DBI::SQL_VARCHAR) then execute with no parameters.
>Or, at the top of the script after the connect set the default bind type to
>SQL_VARCHAR...  I don't like it, though!  It seems that the 
>SQLDescribeParam
>is failing during the second query, but the actual parameter is
>recognized...I can work around this, but it seems to be a bug to me.  What 
>I
>can do is: if SQLDescribeParam fails, set back to SQL_VARCHAR.  That will
>'hide' the error, but I do think it's a bug in their driver...of course I
>can be wrong, but it does seem strange to me.  I think .41 will have a
>workaround -- but as I said, it will only hide the real problem.
>
>Attached is my version of your script, with the mods to avoid the error...
>
>Jeff

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.

Reply via email to