>You would need to use remote views for a C/S solution that use grids.

That's the idea. My customers are rathe spoiled, so far as coding is concerned. The framework I have developed comes with a few builders. To write a prototype application I force them to fill a data dictionary (based on CodeBook) and from then on they are able to create rather complex forms just using the mouse. There are very few choices like: are grids to be based on tables or p-views (default)?. The form has enough logic to establish the update/delete order of the several tables/grids involved; Just one property change in the form will toggle from explicit edit (deafault) to "standard edit" and so on.

The whole thing works trying to convince programmers that mine is just a prototyping tool and that, if you are not trying to do absurdly fancy things, you can view the system as a RAD tool and that the generated "things" can be deployed with just some minor cosmetic changes (mouse work again).

This leads to some interesting results: productivity usually skyrockets at the expense of programming skills so that when a real problem arises (the ones for which we programmers are paid) things just get stuck. On the other hand it's amazing to see a bunch of people turn pragmatic just to avoid difficult situations. And I have discovered that people does not lead intutitively towards OOP but, given the right tool, they all are excellent NNP programmers. (no nonsense programming)

My... ain't I talkative on Sunday mornings?

I hope that this explains the root problem. It really isn't a difficult problem, far form it, but it is rather hard to present it as a canned solution. Well, that's what I'm paid for. I'll put on the thinking hat again and give it another try before telling my people that, for once, they will have to justify their salaries.

Ciao and thanks again.