New development release 1.18_3 of DBD::ODBC

I have just uploaded DBD::ODBC 1.18_3 to CPAN. To see a list of changes 
since 1.18 see below. Since I requested anyone using DBD::ODBC to test 
the last development release I've had two replies - thank you. However, 
I cannot believe there are only 2 users of DBD::ODBC. I maintain 
DBD::ODBC for free in my own time and unlike other DBDs there is a 
massive number of combinations of ODBC drivers and driver managers to 
support so I am making another request to all DBD::ODBC users. Please 
download and at least run a make test on this development release. If 
you don't and it does not work with your ODBC driver or driver manager 
then don't blame me (I'll still try to sort it out but it is best if 
this is done before official releases especially since unless I package 
DBD::ODBC myself for ActiveState you will not get it until it is an 
official release).

=head2 Changes in DBD::ODBC 1.18_4 March 13, 2009

A mistake in the MANIFEST lead to the rt_43384.t test being omitted.

Brian Becker reported the tables PERL_DBD_39897 and PERL_DBD_TEST are
left behind after testing. I've fixed the former but not the latter
yet.

Yet another variation on the changes for rt 43384. If the parameter is
bound specifically as SQL_VARCHAR, you got invalid precision
error. Thanks to Øystein Torget for finding this and helping me verify
the fix.

If you attempt to insert large amounts of data into MS Access (which
does not have SQLDescribeParam) you can get an invalid precision error
which can be worked around by setting the bind type to
SQL_LONGVARCHAR. This version does that for you.

08bind2.t had a wrong skip count.

12blob.t had strict commented out and GetTypeInfo was not quoted. Also
introduced a skip if the execute fails as it just leads to more
obvious failures.

In dbdimp.c/rebind_ph there was a specific workaround for SQL Server
which was not done after testing if we are using SQL Server - this
was breaking tests to MS Access.

=head2 Changes in DBD::ODBC 1.18_2 March 9, 2009

Added yet another workaround for the SQL Server Native Client driver
version 2007.100.1600.22 and 2005.90.1399.00 (driver version
09.00.1399) which leads to HY104, "Invalid precision value" in the
rt_39841.t test.

=head2 Changes in DBD::ODBC 1.18_1 March 6, 2009

Fixed bug reported by Toni Salomäki leading to a describe failed error
when calling procedures with no results. Test cases added to
20SqlServer.t.

Fixed bug rt 43384 reported by Øystein Torget where you cannot insert
more than 127 characters into a Microsoft Access text(255) column when
DBD::ODBC is built in unicode mode.

Martin