Why is Mysqlcheck on 5.1.41 still showing as Innodb table corrupted after a table dump and restore?
The error seems to indicate a problem with the primary key on the table mycompany.fact.  

InnoDB: Page number (if stored to page already) 266102,
InnoDB: space id (if created with &gt;= MySQL-4.1.1 and stored already) 994
InnoDB: Page may be an index page where index id is 0 4668
InnoDB: (index "PRIMARY" of table "mycompany"."Fact")


You can open the dump file in any text editor and remove the primary key constraint from the CREATE TABLE schema definition.  Then once you've restored your database, you can always add the primary key back in.  You would also need to deactivate Foreign Key Checks in your backup file. 

-- at the beginning of the file
SET foreign_key_checks = 0;

-- at the end of the file
SET foreign_key_checks = 1;


This may get your database restored, but if there is a problem with the data in the column you're using as the primary key, then you may see other errors.  

If that didn't work, I would also try 


Backing up all the databases
Stopping MySQL
Delete the ibdata and iblog files
Starting MySQL again
Restore all my databases.


If there is a problem with your InnoDB files, this may be a way to solve it.

The problem could also be deeper and running a fsck on the filesystem that stores your InnoDB files may find corruption on the disk.  Rebooting your computer is one way to easily cause an fsck on all partitions.