>
> 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?
I do -- yes. I should be able to call SQLDescribeParam and have no
problems, I think. Of course I've been wrong before :) -- but this one
seems pretty simple.
Jeff
> >
> >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.
