Bug #12348 Updated: Call to undefined function: mssql_next_result()

ID: 12348 Updated by: derick@php.net Reported By: glenn@websiteresults.com -Status: Open +Status: No Feedback Bug Type: MSSQL related Operating System: linux 7.1 PHP Version: 4.0.6 New Comment: No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Open". Thank you. Previous Comments: ------------------------------------------------------------------------ [2002-01-14 20:29:18] misha@tmolp.com having the same problem. would like to get it fixed asap. is there a patch/fix/workaround. thank you. ------------------------------------------------------------------------ [2001-07-24 19:11:58] fmk@php.net Please notice that the FreeTDS stuff might be broken for SQL Server 2000 and up. ------------------------------------------------------------------------ [2001-07-24 18:37:30] glenn@websiteresults.com We do have a patch that you can roll out in your next release i will send in soon after removing junk comments. ------------------------------------------------------------------------ [2001-07-24 17:18:13] andy@php.net please send your patch (when you are done) to php-dev@lists.php.net ------------------------------------------------------------------------ [2001-07-24 16:45:26] glenn@websiteresults.com the issue is i am using the sybase C files and the function is for the mssql C files. I am working with a coworker to rewrite the sybase C files to support the mssql_next_result function. If you have a version that does please let me know and if we get this to work i will give you the C files for the next release. // error Fatal error: Call to undefined function: mssql_next_result() in /usr/local/apache/htdocs/reporting/reports/rpttrafficdetailsbycpc.dll on line 12 ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/12348 -- Edit this bug report at http://bugs.php.net/?id=12348&edit=1