Jeff and all, I have managed to dig out a little further information that may prove useful for others. The case we are looking at here produces the following for 20SqlServer test 1 and 2:
t/20SqlServer....1..25 Inserting: 0, string length 13 Inserting: 1, 2001-01-01 01:01:01.110 string length 12 Inserting: 2, 2002-02-02 02:02:02.123 string length 114 Inserting: 3, 2003-03-03 03:03:03.333 string length 251 Inserting: 4, 2004-04-04 04:04:04.443 string length 282 Inserting: 5, 2005-05-05 05:05:05.557 string length 131 Retrieving: 0, string length 13 Retrieving: 1, 2001-01-01 01:01:00.000 string length 12 !time Retrieving: 2, 2002-02-02 02:02:02.123 string length 114 Retrieving: 3, 2003-03-03 03:03:03.333 string length 251 Retrieving: 4, 2004-04-04 04:04:04.443 string length 282 Retrieving: 5, 2005-05-05 05:05:05.557 string length 131 not ok 1 f ne foo Please upgrade your ODBC drivers to the latest SQL Server drivers available. not ok 2 The first obvious problem is the timestamp "2001-01-01 01:01:01.110" inserted is retrieved as "2001-01-01 01:01:00.000". The second problem is that test 2 inserts "foo" and gets back "f". I have emails with you regarding the second issue which was finally tracked down to a SQL Server problem and an upgrade to MDAC 2.7 fixed it for you (and the person who originally reported it) but I can't find anything regarding the first issue other than the comment in the test that says: "the times chosen below are VERY specific to NOT cause rounding errors, but may cause different errors on different versions of SQL Server." For reference the version of the SQL Server driver being used in this case is 2000.80.194.00. A version of the SQL Server driver that works is 2000.81.9030.04. I cannot find anything on MS's site but I can definitely confirm an upgrade of the SQL Server ODBC driver to the one in MDAC 7 fixes the problem. Jeff, you might want to add something to the "Please upgrade your ODBC drivers..." message to help here or mention the buggy 2000.80.194.00 driver. Martin On 11-Jun-2003 Jeff Urlwin wrote: >> >> Hi, >> >> Does anyone know why the 20Sqlserver test in DBD::ODBC >> recommends upgrading your ODBC driver? - Jeff. > > Err. If I recall correctly, those tests failed with MDAC 2.6 or less and > worked with MDAC 2.7. I can't recall why, but I thought I was getting > strange responses and when I upgraded, it worked. > >> >> t/20SqlServer....Please upgrade your ODBC drivers to the >> latest SQL Server drivers available. FAILED tests 1-2, 6 >> >> What was the purpose of the test? It appears to >> create a temporary table, insert some values and retrieve >> them again to make sure they are correctly inserted. >> >> I am in the process of getting verbose output for the test >> but if someone knows the reason for the upgrade advice I'd >> love to know. >> > > I wish I remembered more and documented it... > > Regards, > > Jeff -- Martin J. Evans Easysoft Ltd, UK Development
