>However, since the arrival of views I chose to let my tables in peace, and did all my modifications on views, letting tables either accept or reject those modifications. In doing so, I rest assured that tables only recieve valid data by update from views after user is done modifying the data.

If the tables only receive valid data, why would they ever reject a change from a view?

>One of the things I don't like about modifying tables is those unexpected crashes, often performed by unexperienced users, that leave tables with incomplete data. It has resulted in a corrupt table a few times, and one corrupt table is one too many.<

When you use a view, the base tables are open as well. As soon as you TableUpdate() your view, the base tables are updated. I don't see how using views helps, here.

Views can be tricky. For example, when you add a record to a view, table defaults for fields are not automatically applied. You can write some code to get the defaults out of the table's definition in the database, but that's not necessary if you just use tables in the first place.