Question : MVC Modeling

I currently use an MVC-type pattern with Classic ASP via SQL/XML for large (as measured by page count) biz apps and am looking at possibly transitioning to a .Net MVC2 application.  In looking at some sample apps, the models usually reference the tables directly, whereas, I don't allocate user permissions to tables directly, but instead grant permissions only to functions, views, or stored procedures.  Will the MVC2 app work for this type of scenario where direct table access is not permitted?  I need to be able to use a table return function (or view) for query, an update stored procedure for changes, and a different sp for deletes.  Is LINQ for SQL going to be of any use?  Is there a sample project that shows how the model portion would look?

Answer : MVC Modeling

The MVC framework is completely separate from your data-access technique so you can use whatever type of data access layer you want with it, including the plain old ADO.NET classes. A lot of the samples use direct table access because that is the way the wind is blowing at the moment and it offers the most flexibility.
Linq to SQL works pretty well with stored procedures so may well be of use to you.
The MVC Framework pretty much focusses on managing the views and controllers. The model part is left up to you to implement however you see fit.