#38784 [Bgs]: odbc_fetch_row call

ID: 38784 Updated by: kalowsky@php.net Reported By: jkeagle at knology dot net Status: Bogus Bug Type: ODBC related Operating System: Windows XP PHP Version: 4.4.4 New Comment: While I agree the response wasn't terribly helpful, this also isn't a support forum. There are better avenues for that where functionality can be explained. Currently, you've written very little that has shown a bug in PHP itself (I'll cede a bit better documentation as a tangential to the original statement). Previous Comments: ------------------------------------------------------------------------ [2006-09-13 16:59:47] jkeagle at knology dot net If I knew how to fix the odbc_fetch_row call I wouldn't have submitted the problem. Thanks for nothing. ------------------------------------------------------------------------ [2006-09-13 16:54:04] keagle at westar dot com You people are UNBELIEVABLY helpful .... NOT!!!!! ------------------------------------------------------------------------ [2006-09-13 15:38:46] kalowsky@php.net Why are you trusting odbc_num_rows? And fix your odbc_fetch_row call. ------------------------------------------------------------------------ [2006-09-12 18:04:20] jkeagle at knology dot net I tried the odbc_errormsg() call and got an empty string. I also tried odbc_error() and got the same result. The problem is that a negative value is returned for each call to odbc_fetch_row as if there are no rows to fetch. What is misleading is that I can execute odbc_num_rows($res) and get 662, which is what I expected to get. Also, a call to odbc_num_fields($res) was called and returned the expected value of 2. What I don't understand is why I can't "fetch a row" out the same result variable ($res). Everytime I make a call to odbc_fetch_row($res), a negative value (0) is returned. ------------------------------------------------------------------------ [2006-09-12 16:45:59] tony2001@php.net Use odbc_errormsg() to get the reson why it fails. ------------------------------------------------------------------------ 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/38784 -- Edit this bug report at http://bugs.php.net/?id=38784&edit=1