weird mysql issue...

[sandstig]

I just ran myisamchk on my database tables, and for some reason, I can't seem to search my user table. I'm running on MySQL 4.0.18 on WHM/CPanel.

The table and its indexes appear to be intact and I didn't see any useful error messages while I was running myisamchk.

The following error appears in phpMyAdmin, when I try to view the user table though:

Warning: mysql_query(): Unable to save result set in /home/pex/public_html/admintools/dbadmin/sql.php on line 414

Warning: Cannot modify header information - headers already sent by (output started at /home/pex/public_html/admintools/dbadmin/sql.php:414) in /home/pex/public_html/admintools/dbadmin/libraries/ob.lib.php on line 65

Warning: Cannot modify header information - headers already sent by (output started at /home/pex/public_html/admintools/dbadmin/sql.php:414) in /home/pex/public_html/admintools/dbadmin/header.inc.php on line 27

Warning: Cannot modify header information - headers already sent by (output started at /home/pex/public_html/admintools/dbadmin/sql.php:414) in /home/pex/public_html/admintools/dbadmin/header.inc.php on line 28

Warning: Cannot modify header information - headers already sent by (output started at /home/pex/public_html/admintools/dbadmin/sql.php:414) in /home/pex/public_html/admintools/dbadmin/header.inc.php on line 29

Warning: Cannot modify header information - headers already sent by (output started at /home/pex/public_html/admintools/dbadmin/sql.php:414) in /home/pex/public_html/admintools/dbadmin/header.inc.php on line 30

Warning: Cannot modify header information - headers already sent by (output started at /home/pex/public_html/admintools/dbadmin/sql.php:414) in /home/pex/public_html/admintools/dbadmin/header.inc.php on line 32
I'm speaking to the guys at my hosting company right now, and they say they've never ever run into anything like this. Have any of you guys encountered anything like this before? I got an earlier error saying my keys weren't right, but that was it.

[sandstig]

Using the REPAIR TABLE (http://www.mysql.com/doc/en/REPAIR_TABLE.html) command fixed the problem. Any plans on including this in future guides? Seems more handy than the myisamchk and isamchk commands.

[eva2000]

the listed *.php files check to see if there's whitespace/blank lines in them which is indicated by the message Cannot modify header information - headers already sent by

it isn't a mysql error but php error