Our app currently has over 20 grid classes based off three base grid classes. Each column in the grid could have its own special behavior ( like numeric range checking, lookups, date validation, inout masks etc... ) The users do all of their data entry on the grids via clicking "New" buttons or mneumonics like F4 key for a new record. We also allow data entry via a CE device or bulk imports from files.

If you design them right and use lots of meta data ( we use Stonefield ) and do not put huge amounts of code in the grid itself it is rather quick and efficient. Our code is very abstract and all the girds run off of SQL updateable views ( now Cursor Adapters ) that we build on the fly to restrict the columns to only the ones the user chooses and their related columns. In our target industry if we made out users go to a form style data entry we would lose our client base. Form style entry is good for inventory type systems, patient style systems, or banking where you are only intested in data that applies to one entity, like a PO number or customer name. In the data we store each record relates to the records before and after them in some form or another on the grid and the users like seeing them.

Wayne, maybe you need some outside UI consulting ( or at least make a detailed study ) to steer you the right path as to what fits you client base. Making you clients work to hard to get their data in is a good way to push then away.