I have exactly the same configuration as you do, except for the fact that I
use PHP as an Apache module and not as CGI. I have no problems at all.
Running PHP as an Apache module and it is more efficient than the CGI
version.

On the other hand, there are other several things you can try:

1. Use mssql_get_last_message() to make sure that the error is not being
generated at ths SQL Server.

2. Use one connection for each query, closing all your cursors and
connections before opening a new one.

3. If nothing seems to work, this code will help:

/*1. Hide warnings*/
    error_reporting(E_ALL & ~E_WARNING);
/*2. Run query twice before giving up with an error message*/
    mssql_query($myQuery) or msssql($myQuery) or die("Query Failed: " .
$myQuery . "<br>" . mssql_get_last_message());
/*3. Turn warnings back on */
    error_reporting(E_ALL);

That way, you will avoid all warning messages, and will run twice the query
that produces a warning, halting execution if an erro occurs.

Cheers. PD: Eres mexicano?


-- 
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to