Warning: mysql_result(): Unable to jump to row 0 on MySQL result index 7

Question

i am getting the error
Warning: mysql_result(): Unable to jump to row 0 on MySQL
result index 7
please can smoeone tell me where i might be going wrong?
thanks
<?
include("dbconfig.php");
//get reg code
$findstring = trim($_GET[s]);
if ($findstring != "") {
//find reg code in memberslist
$res = mysql_query("SELECT code FROM users WHERE
code='$findstring' LIMIT 1");
if (mysql_num_rows($res) == 1) {
$res = mysql_query("UPDATE users SET code = 'done', password
= 'catanddog' WHERE code='$findstring' LIMIT 1");
//upto here all is ok.
$res = mysql_query( "SELECT email FROM users WHERE
code='$findstring' LIMIT 1" ) or die ( mysql_error() );
// the line above is almost the same as the request near the
top of this code, eccept that it now looks for the email field not
the code field.
$email = mysql_result( $res, 0 ) or die( mysql_error() );
echo('a.'.$email.'.a');
$res = mysql_query("INSERT INTO anothertable (email, field1,
field2) VALUES ('$email', '', '')");
?>
<p>Thank you for completing you registration
process.</p>
<?
} else {
?>
<p>Sorry but this is an illegal action.</p>
<?
mysql_close;
?>
and this is my database entry.
CREATE TABLE `users` (
`code` varchar(32) NOT NULL default '',
`email` varchar(40) NOT NULL default ''
) ENGINE=MyISAM DEFAULT CHARSET=latin1;
-- Dumping data for table `users`
INSERT INTO `users` VALUES ('123',
'[email protected]');

Answer 1

shame though :( ... I can live with it ... perhaps you can let me know
when/if there's a fix in the future.There will be no fix forthcoming on our side, because I can say with
99.9% certainty this is not a Kodo bug. We do batching the same way,
using standard JDBC calls, on every database that supports it. The fact
that the driver you're using is the only one with problems strongly
indicates it's a driver bug (you wouldn't believe how common these are;
even commercial DBs like Oracle often fail to implement large portions of
the JDBC spec). We've found a lot of bugs in Postgres drivers in
particular, IIRC.
I recommend you play around with different drivers. First, make
sure you have the very latest 7.3 driver. If you do, downgrade to the
7.2 driver (you can stick with the 7.3 DB version; I seriously doubt it's
a DB bug, and I also doubt the protocols have changed between 7.2 and
7.3, so the old driver should work).
Since it's an open source project, you could also submit the bug to the
JDBC driver authors and they'll probably actually pay attention to it.
You could even try to patch it yourself.