Lance, > Platform: RedHat 7.3 Ok, I test w/SUSE 7.x
> DBI: Latest Version My version is 1.30 > DBI::ODBC: Version 1.0 > Using the EasySoft ODBC Bridge as the transport to the > Microsoft Server... > latest version. I tested this version using Easysoft's OOB version 1.0.0.32, unixODBC 2.2.3 and SQLServer 2000. Also, I'm using MDAC 2.7 on the server and my Windows based clients, which I *highly* recommend... What version(s) of OOB, unixODBC and SQLServer are you using? Also, listing the version of the SQLServer ODBC driver on the server may be helpful (get it from control panel/administrative tools ODBC applet) [snip] > Unable to find a suitable test type for field COL_C at > t/ODBCTEST.pm line 63. dubious This is the root of the problem. Can you run mytest/testfunc.pl from the DBD-ODBC distribution and send me the output? If testfunc.pl fails with a "right truncation" as in: "[unixODBC][][Microsoft][ODBC SQL Server Driver]String data, right truncation (SQL-01004)" let me know. > Test returned status 255 (wstat 65280, 0xff00) > DIED. FAILED tests 3-17 > Failed 15/17 tests, 11.76% okay > t/03dbatt...........1..16 ok 1 ok 2 DBD::ODBC::db do failed: > [unixODBC][Microsoft][ODBC SQL Server Driver][SQL > Server]Invalid object name 'PERL_DBD_TEST'. (SQL-42S02)(DBD: Execute > immediate failed err=-1) at t/03dbatt.t line 112. This is because the test can't find the right information. It may be nothing's really wrong, but I'm skeptical at the moment. I can't believe that SQL Server is reporting that it doesn't have a native type for SQL_LONGVARCHAR. Rather, there must be something going on which is causing the SQLGetInfo to get a data truncation. Also, if you can, try running testfunc.pl on the server itself to see what it reports. Thanks, Jeff
