FreeTDS Development Group

["Robin Smith" <Robin AT ndigital.com>]

> It might be time for more detailed information.  A TDSDUMP log will show
> what calls are being made to the ODBC driver and what happens next.  
> Maybe in conjunction with the ODBC trace that will reveal something.  
 
Here are the logs. They are big, so I upped them to our website. There's four 
logs in total.
 
sql.isql.log and freetds.isql.log:
http://www.ndigital.com/tmp/sql.isql.log 
http://www.ndigital.com/tmp/freetds.isql.log 
These are logs of it running the select statement successfully from isql 
using the server definition in FreeTDS
 
sql.php.log and freetds.php.log:
http://www.ndigital.com/tmp/sql.php.log 
http://www.ndigital.com/tmp/freetds.php.log 
These are logs of it running the same select statement from the PHP page 
using the server definition in FreeTDS.
 
The main difference that I see is the "sp_cursorfetch" nrows error I 
mentioned before. That does not happen during the isql version. However, I 
have an untrained eye for these types of logs ;)
 
Thanks
 
Robin
 
-----------------------
Robin Smith
Senior Manager, Information Technology
NDI
103 Randall Drive
Waterloo, ON, Canada N2V 1C5
Telephone: +1 (519) 884-5142 ext. 224
Toll Free: +1 (877) 634-6340
Global: ++ (800) 634-634-00
Facsimile: +1 (519) 884-5184
Website: www.ndigital.com ( http://www.ndigital.com/ )
----------------------