Re: MS SQL error handling...

Have you tried writing a wrapper function for mssql_query(), something like: my_mssql_query( $query, $link_id){

        global $php_errormsg;
        ob_start();
        $result = mssql_query( $query, $link_id );
        if( !$result ){
                $php_errormsg = ob_get_contents();
        }
        ob_end_clean();

        return $result;

} morgan At 09:48 AM 3/30/2001, Christian Dechery wrote:

isn't there a better way to handle MS SQL error messages? I can't even fetch them... look at these warnings... they only show in development side, I don't want warnings on the production site, so I turn them off with error_reporting()... Warning: MS SQL message: There is already an object named 'FK_genre_genre' in the database. (severity 16) in S:\Inetpub\wwwroot\liquid\liquid_catalog_update.php on line 607 Warning: MS SQL message: Could not create constraint. See previous errors. (severity 16) in S:\Inetpub\wwwroot\liquid\liquid_catalog_update.php on line 607 Warning: MS SQL: Query failed in S:\Inetpub\wwwroot\liquid\liquid_catalog_update.php on line 607 Could not create constraint. See previous errors. <-- this is what I get from mssql_get_last_message() MS SQL: Query failed <-- this is the content of $php_errormsg you guys have to agree with me, that neither of them help me at all.... why can't I fetch the first Warning, the one with the really interesting content???