Hi, As most of you are aware a lot of people are using the FreeTDS libraries (http://www.freetds.org) along with DBD::Sybase to access MS-SQL servers from non MS hosts (unix, linux).
However, due to FreeTDS not implementing all of the Sybase Client Library API, and to the fact that not all of the TDS protocol supported by MS-SQL has been decoded there are a number of things in DBD::Sybase that fail when used with FreeTDS. I have been thinking of forking DBD::Sybase and creating a dedicated DBD::FreeTDS driver that would be geared towards working specifically with FreeTDS. The FreeTDS folks will still continue to improve things so that more functionality in DBD::Sybase is covered, but for now I get a *lot* of email regarding various failures in DBD::Sybase that are due to missing or broken functionality in FreeTDS. In addition there are some people who need to access Sybase and MS-SQL servers from the same script, and for those the limitations of FreeTDS for the Sybase side might not be acceptable - hence the need for two different modules using the FreeTDS and Sybase libraries, respectively. Do people here see this as a good idea? Michael -- Michael Peppler Data Migrations, Inc. [EMAIL PROTECTED] http://www.mbay.net/~mpeppler Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or long term contract positions - http://www.mbay.net/~mpeppler/resume.html
