basic but....

[eluser]xwero[/eluser]
If you have a table with a lot of fields chances are there is going to be more than one form that alters another slice of the fields. So if i understand you well you would create a method for each view in which case you couple the model methods to a certain view file making the methods less reusable?
And what would you do with data that is required on one form but not on another or that has to match another field in on form and not on another?

I think there a several scenario's where it's beneficial for the model code not to have the validation in the model methods but in a separate layer, like the Akelos solution if i'm not mistaken or in the controller. This is why i made the compromise.