ter your first inserted.
> It doesn't matter that you use (mssql_free),
> you still need to close
> the link first.
> The function of mssql_free is just free up the
> content of that variable,
> but it won't close the link for U.
>
> Kelvin.
>
> &q
I got the error messages with your help. Unfortunatly,
I didn't see any problem in these message. Here is the
messages on my browser by loading the php file:
Changed database context to 'pubs'.
Changed database context to 'pubs'.query2 failed!
Changed database context to 'pubs'.query3 failed
Hi,
How can I see the error message from browser? My code
is like this:
I got "query failed" on the browser screen and nothing
else. Here is some value I got from phpinfo():
Configuration
PHP Core
Directive Local value Master value
display_er
1 failed");
> sybase_free_result($result);
>
> $result=sybase_query("insert into pub_info
> values(0001,null,'test')") or
> die("query2 failed");
> sybase_free_result($result);
>
> $result=sybase_query("select * from pub_info");
&g
Please take a look into my simple php code. Why does
this program die on "query2 failed" but a new record
acturally is inserted into table "pub_info"?
I asked this question last week, but didn't get any
answer so far. If you don't see any problem in there,
please let me know. This is my last try
the person doing freetds setup on this Unix
machine. Do you think this is a freetds related
problem?
--- olinux o <[EMAIL PROTECTED]> wrote:
> test
>
> --- jong jong <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I am working on Unix(Solaris 2.8) with Apache
I have to correct this:
The following stored procedure did add 2 records into
"mytable" after I called sybase_query("exec
SP",$conn). But it just returned "false" like what I
said yesterday. Anyway, 2 records went to my database.
That's better than 1. So I don't care this "false".
SP:
CREATE PROC
Hi,
I am working on Unix(Solaris 2.8) with Apache 1.3 and
php4. I need to connect MS-SQL Server without ODBC. I
know there is an option that using freetds but I
haven't tried it yet.
Someone told me that sybase functions can work with
MS-SQL Server directly. So I called sybase_xxx()
instead of m
