Hi Jim,

>I haven't met a user yet who "likes" to browse data. I have met a lot of developers that do.

I thought it was the other way round. Developers have a hard time getting the grid to work they want it to, and so they prefer to avioid it.

>The grid presents data in a data centric fashion, while most users are more interested in getting a job done. An interface that helps the user get their job done will not necessarily use alot of grids.

I think it depends on the nature of the application. For e.g. creating something as simple as an invoice would definitely need a grid. Not because its the only solution (there are many <g>) but because it provides a synonymous interface like manually writing the invoice.