Add shortest possible example script which can be used
to reproduce this into this report.

Update: with a bigger query like the following (returning 2K+ rows with sqsl based on freetds), I always get
1 is not a valid Sybase-Link resource in <b>test.php</b> on line <b>9</b> when mssql_query()ing, using pconnect() or connect(). Hence, the bug is definately not in freetds, but in sybase_ct.
Side note, I am using php4.0.4pl1 with sybase/freetds (not _ct) on another debian (2.2, apache/php self-compiled)machine and it works just fine.


<?
mssql_pconnect("server","user","pass");
viewdb("SELECT
RegNumber,ISCorporate,Customers.FirstName+Customers.MiddleName+Customers.LastName,Customers.Address,Customers.City,
Customers.State,Customers.ZIP,Customers.HomePhone,Customers.Fax,NickName
from Customers INNER JOIN SalesPersons on Customers.SalesPersonID=Salespersons.SalesPersonID");


function viewdb($query) {
        $r=mssql_query($query);
        if (!$r) {
                print "No results";
                exit;
        };
        print "<p align=center><table border=1>";
        while ($res=mssql_fetch_object($r)) {
                print "<tr>\n";
                if (!isset($fields)) {
                        foreach (array_keys(get_object_vars($res)) as
$n=>$val) {
                                if (!($n%2)) continue;
                                $fields[]=$val;
                        print "<th>$val";
                        };
                        print "<tr>\n";
                };
                foreach ($fields as $field) {
                        print "<td>".$res->$field."\n";
                };
        };
        print "</table>";
};

Can this be reproduced with a later version of freetds and/or?

R.

Fixed in latest php code.