[eluser]jdfwarrior[/eluser]
Agreed. I've never even heard of someone restricting a Model to a single table.
"Models are PHP classes that are designed to work with information in your database."
They are just there to provide you with a place to store code for database work as opposed to having everything in the Controller. I've never split mine up into a Model for an individual table. I split for functionality. Like, having a User_model to handle all user related actions such as, login authentication, registration, editing user settings, etc