> 
> All,
> 
> So far I have perl executable 5.8.0. Do i have to upgrade 
> perl.exe to 5.8.5 version to test DBD::ODBC 1.13 again?
> 

No, you shouldn't need to.

Regards,

Jeff
> 
> 
> > 
> > 
> > All,
> > 
> > I am trying to use Perl with DBI/DBD and Datadirect ODBC to
> > import datafile on unix to remote windows-based SQL server RDBMS. 
> > I have installed DBI-1.45 and Datadirect (www.datadirect.com) 
> > ODBC drive for SQL server DB on my Redhat 9.0 Linux. So far 
> > DataDirect SQL ODBC drive on linux is working and can be 
> > associated to remote SQL server DB. Now I have problem to 
> > configure the DBD:ODBC 1.11 integrated with DataDirect ODBC 
> > to connect SQL server DB. I have read the documentation of 
> > knowledgebase on www.datadirect.com. The final test step make 
> > test  awalys failed with attached message. Could someone 
> > advise me on it? Thanks a lot!
> 
> That's OK.  It seems that the data-direct drivers tell us 
> that it doesn't support multiple statements, yet we expect 
> SQL Server to support it.  
> 
> You can safely make install the version you are using, but 
> you may have some strange problems with some complex 
> situations using SQL Server and multiple statements.
> 
> In DBD::ODBC 1.13 I put a lot of effort into changing the 
> tests to use Test::More.  If you have some time and can try 
> 1.13 with TEST_VERBOSE, I could possibly make the tests work 
> a bit smarter about it, but the core functionality looks good 
> from here.
> 
> Regards,
> 
> Jeff
> 
> 
> 
> CONFIDENTIALITY NOTICE:
> If you have received this e-mail in error, please immediately 
> notify the sender by return e-mail and delete this e-mail and 
> any attachments from your computer system.
> 
> To the extent the information in this e-mail and any 
> attachments contain protected health information as defined 
> by the Health Insurance Portability and Accountability Act of 
> 1996 ("HIPAA"), PL 104-191; 43 CFR Parts 160 and 164; or 
> Chapter 181, Texas Health and Safety Code, it is confidential 
> and/or privileged.  This e-mail may also be confidential 
> and/or privileged under Texas law.  The e-mail is for the use 
> of only the individual or entity named above.  If you are not 
> the intended recipient, or any authorized representative of 
> the intended recipient, you are hereby notified that any 
> review, dissemination or copying of this e-mail and its 
> attachments is strictly prohibited.
> 
> 

Reply via email to