I agree that using grids in a view is not a bad thing. In fact I use views in grids all the time and never have any problems. I believe what people are getting confused about is using 1 view to represent all the parent and child data. In this instance you should not use one view, but multiple views: 1 for the parent information and another with the child information that you wish to display in a grid.

I believe that views are the way to go:
1) Buffering and transaction processing allow you to really control when data is written to your base table (you can do this with base tables, but I believe it is much better when used with views)
2) You can update/display multiple fields from related tables without having to specifically coding for the different tables. You decide all of this when you create the view.
3) This prototypes your system for eventual migration to a client/server architecture.
4) Data integrity. Even if you never go client/server, adding,editting, and deleting information through views keeps your data in good shape. For example, I use views in my file-server application that is run by 40 people across a WAN. I have had the file-server "lock" solid twice. I have users that out of the application or just turn off the power to their machine god knows how many times, and I have not lost 1 ounce of data or had one bit of data corruption. The system has been up and operational since March and I have a good deal of information going across the WAN since it is a perpetual inventory system for the manufacturing process. This alone makes the views more than worth it to me.

Perceived drawbacks:
1)Especially without using SYS(3054,11) to rushmore optimize the views, views do take a little longer to retrieve data than just straight lookups on the tables, but the time difference is pretty insignificant (in file-server bases apps).
2) When your creating the views and coding your interfaces you have to know the relationships between your tables and take time to plan your views properly.
3) Views are static in nature. If you want the most up-to-date data, you will need to consistently REFRESH or REQUERY the view. However, I do not see this as a problem with data entry, because your editting a snap-shot of the data 99% of the time anyways.

Don't know if this helps you, but I hope it does.

I would give my left arm to be ambidextrous!