Skip to Content.
Sympa Menu

freetds - Re: conflicting types for `RETCODE'

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: Re: conflicting types for `RETCODE'
  • Date: Tue, 20 Aug 2002 11:57:11 -0400


> From: Benji Spencer [mailto:ben.spencer AT moody.edu]
> Sent: August 20, 2002 11:01 AM
>
> <?
> $ms_conn=mssql_connect("interface_name",'username','password);
> ?>

No closing quote on the password?

>
> It comes back with "Warning: Sybase: Unable to connect in
> /usr/local/apache/localhost/htdocs/go.php on line 2"
>
> It almost seems like it doesn't know where the interfaces
> file is. I do
> have the interfaces file defined in the php.ini as
>
> sybase.interface_file="/usr/local/freetds/interfaces"

A guess from a non-PHP guy; I don't know why PHP wants to know where the
interfaces file is. FreeTDS will prefer its freetds.conf, installed in
sysconfdir. FreeTDS of course can't know it's being called from PHP, and
won't look for an interfaces file unless it can't find freetds.conf.

I think this behavior became more flexible (per the UG's description) after
0.53.

You'll want either to delete freetds.conf, or to make sure it agrees with
interfaces.

Also, if you turn on logging, you might get a clearer picture of what's
going on.

HTH.

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.






Archive powered by MHonArc 2.6.24.

Top of Page