We are re-writing an application that has languished without maintenance for 7 years. Our customer’s requirement is to provide data entry screens with grids. Each grid will have a different structure (database fields, number of columns, differing columns with combo boxes, date pickers, etc). I have a little over 80 screens (40 data entry and 40 error editor) to create and each screen has the exact same functionality other than the data displayed in the grid (pop-up menus, toolbars, etc). I would like a way to save the entire layout, bindings, etc so that I will actually only have one data entry screen and one error editor screen and then can load the appropriate grids layout, structure, etc.. In the older application using a ComponenetOne (was Apex) dbTrueGrid I was able to do the following:
Thanks
Richard
The only thing I see here that would not be saved in the grid layout is the data source of the dropdowns. The column order, links from the column to the dropdown control, and formatting of the column are all saved as part of the layout.
There's nothing in the grid that can save the data source on a control outside the grid, so you would need to handle that manually.
If you want to include this information in the same file as the layout, then what you can do is save the layout to a Stream. You can then add information to the stream either before or after the layout and use that same information when you load the layout.