Hi Dan
I've been trying out with the snapshots from snaps.php.net/win32 but I still
have the same errors. The actual snaps of 4.2 don't work either.
Christoph
I'm looking into these problems right now. Please be patient. A recent
slew of bug reports suggests that there might be some stuff
the distributions have all worked. Thanks.
Ryan
-Original Message-
From: Andreas Karajannis [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 24, 2002 5:16 PM
To: Dan Kalowsky
Cc: Ryan Jameson (USA); [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] odbc problems in 4.2
Dan Kalowsky wrote:
Hi Ryan,
Okay
To: Dan Kalowsky
Cc: Ryan Jameson (USA); [EMAIL PROTECTED]
Subject: Re: [PHP-DEV] odbc problems in 4.2
Dan Kalowsky wrote:
Hi Ryan,
Okay did a little looking over the odbc_fetch_row code, and it should
reset the result-fetched to whatever the second argument (if one is
provided
If this is easy for anyone could someone verify that:
odbc_fetch_row($rs,0);
...does not reset the result set in version 4.2? From what I can tell it doesn't work
at all. I want to be certain that we cannot upgrade to 4.2. If someone has another way
to reset an ODBC result set I'd love to
Title: RE: [PHP-DEV] odbc problems in 4.2
-Original Message-
From: Ryan Jameson writes:
(shhh... I tried to get them to use MySQL ... they are scared
of free stuff. I'm just glad they let me use PHP). Thanks!
Thats a riot.
Tell them to send a cheque to both the MySQL
Hi Ryan,
Okay did a little looking over the odbc_fetch_row code, and it should
reset the result-fetched to whatever the second argument (if one is
provided) is. This variable is how the ODBC result system handles where
it currently is in the cache. Now the catch is that odbc_result checks
this
Dan Kalowsky wrote:
Hi Ryan,
Okay did a little looking over the odbc_fetch_row code, and it should
reset the result-fetched to whatever the second argument (if one is
provided) is. This variable is how the ODBC result system handles where
it currently is in the cache. Now the catch is