<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>RE: [Kc] Problem with Sybase.pm</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Otterson,Gary wrote:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Has anyone out there had any experience with the DBD::Sybase</FONT>
<BR><FONT SIZE=2>> module on Win 2000. I had been running it on an identical</FONT>
<BR><FONT SIZE=2>> system for 4 month one of the disks crashed I had the data</FONT>
<BR><FONT SIZE=2>> backed up but I lost the Perl install and the modules. I</FONT>
<BR><FONT SIZE=2>> thought no big deal but I can't get the DBD-Sybase module</FONT>
<BR><FONT SIZE=2>> to install with the PPM or if I install it manually the</FONT>
<BR><FONT SIZE=2>> scripts fail. I have tried every combination of version of</FONT>
<BR><FONT SIZE=2>> Perl code, DBD module and DBI module and nothing works.</FONT>
<BR><FONT SIZE=2>> Before I go into any more detail I was wondering if anyone</FONT>
<BR><FONT SIZE=2>> out there has any experience with this or if this is even</FONT>
<BR><FONT SIZE=2>> the place to ask a question. I have been searching through</FONT>
<BR><FONT SIZE=2>> google for two days and I can't find anything. </FONT>
</P>
<P><FONT SIZE=2>I've never actually used DBD::Sybase on a Win32 OS for the purpose of talking to a Sybase database. What I have done, is used DBD::Sybase on Linux with FreeTDS to talk to an MSSQL database... Though DBD::ODBC wound up being a better fit for working with MSSQL servers.</FONT></P>
<P><FONT SIZE=2>Knowing your version of perl, DBD::Sybase, ct-lib (open client libraries), and Sybase or MSSQL Server might be useful... And the actual test failures and errors encountered...</FONT></P>
<P><FONT SIZE=2>There are lots of things that can go wrong. There are environment variables like SYBASE, SYBASE_OCS and TDSVER that need to be set appropriately... The PWD file in the source directory must be modified to contain a valid user, password, and server or the test scripts _will_ fail. A manual build after a very careful reading of all available documentation may be your best bet.</FONT></P>
<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Garrett Goebel </FONT>
<BR><FONT SIZE=2>IS Development Specialist </FONT>
<BR><FONT SIZE=2>ScriptPro Direct: 913.403.5261 </FONT>
<BR><FONT SIZE=2>5828 Reeds Road Main: 913.384.1008 </FONT>
<BR><FONT SIZE=2>Mission, KS 66202 Fax: 913.384.2180 </FONT>
<BR><FONT SIZE=2>www.scriptpro.com garrett at scriptpro dot com </FONT>
</P>
</BODY>
</HTML>