ID: 8358 Updated by: kalowsky Reported By: [EMAIL PROTECTED] Old-Status: Feedback Status: Closed Bug Type: ODBC related PHP Version: 4.0.4 Assigned To: Comments: no user feedback. considered fixed in cvs. if this untrue, please reopen the bug. Previous Comments: --------------------------------------------------------------------------- [2001-03-28 10:43:15] [EMAIL PROTECTED] Have you tried this with the latest RC (4.0.5) of PHP? I believe there has been some work done on the ODBC and OpenLink integration. --------------------------------------------------------------------------- [2000-12-21 11:50:46] [EMAIL PROTECTED] ./configure --with-openlink=/usr/local/openlink make There are some queries that will not work with OpenLink/PHP4/Linux and MSSQL 7. For example, any use of SOUNDEX() will fail, as well as odd things like if queries end in a semicolon (";"). These exact same queries work with the "odbctest" program that ships with OpenLink, which leads me to think it is an issue with the way PHP4 interacts with OpenLink. This exact problem has been reported by several other people on the PHP mailing list and on the OpenLink newsgroup servers. resolution: In my attempt to track down this problem, I compared php_odbc.c with what the odbctest program does. The code is similar in some ways and not in others. After tweaking several options, I found that if I undefine HAVE_SQL_EXTENDED_FETCH everything works great with PHP4/Openlink, including the queries with things like SOUNDEX()/etc that would not work previously. This is also using odbc_prepare/execute. The only problem I've found with this change is that queries will sometimes fail if you don't use odbc_free_result frequently. #undef HAVE_SQL_EXTENDED_FETCH --------------------------------------------------------------------------- ATTENTION! Do NOT reply to this email! To reply, use the web interface found at http://bugs.php.net/?id=8358&edit=2 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]