>Hi all,
>
>Would like to get some concept ideas and/or "don't do that" comments re a new screen that a customer has asked me to do a proof of concept on. I will attach a picture as that makes it easier.
>
>A bit of background: they do up quotes for a client showing them how much money they would get paid with different annuities e.g. Options A, B or C. Currently they load one quote at a time in an editing screen. The quote has a header record (name, birthdate etc) and then a grid with child payment in it (because you could be getting multiple streams of payments).
>
>They would like this to change so that they can see multiple quotes at a time on the same page - because their annuity analysts want to see all quotes to get a "big picture" of what the client is getting for all the options.
>
>They want the option to be able to push a button and add a quote to the screen - basically adding a separate header row and then a grid of child rows. I would like to do this programmatically such that when they start, only the one set of grids show and then they can keep adding. But my current setup has one view for the header stuff and another for the payments stuff. I would have to have one set of views for each "quote" shown on the screen - all with different aliases.
>
>So I know I can instantiate new objects for these at run time but can I then bind the controls to their data sources at run time. I know there is a .BindControls property but reading up on that, it seems to be mainly used for delaying the binding. It doesn't seem to be for the purposes of adding controls and opening a view and then binding the view to the controls at run time.
>
>Any ideas? I have done a mockup for them - hopefully I have not over-promised :-)
>
>Albert
Have you thought of using a grid?