Hi Tim,

>
>There seems to be a bug in the BLG. I was setting up some business objects using existing stored procedures and when I went to look at some of the parameters in the grid on the right hand side of the screen I got an error dialog titled 'DataGridView Default Error Dialog' with the error message 'System.ArguementException: DataGridViewComboboxCell value is not valid'. This error dialog then repeated (30 - 40 times) until I gave up and used Task Manager to kill the BLG app.
>
>I lost everything I had done up to that point in the BLG and had to start over.
>
>Which reminds me of another thing. Perhaps a future enhancement to the BLG could be the ability to store some template information for business objects in a persistant XML file. Right now if I go back into a existing business object to add a field or make some other change, I have to re-enter the description strings for each field, etc. It would be nice if some of this information could persist outside of code to make modifying business objects easier.
>
>Tim

I think the persisting previous settings would be really nice also and would welcome that addition. Don't forget however if you need to make a minor adjustment to a BLG generated object you can always make those changes manually. Also if you only need to change the entity for instance you don't need to regenerate all the objects. Typically, if I add a new field to the table I just add the extra property to the entity object myself. I almost never regenerate the business object itself as my code is in there. All the generated objects are super easy to create completely by hand if need be and even easier to modify if needed. Just another couple of ideas to ponder.
Tim B.