I like your method. I do use the partial classes so it's no big deal for me to rerun the BLG, and another reason I do it is because I have it create the Stored Procedures too. I know I could make those changes by hand but now there's more than one thing to change so I just let the app do it for me. But for small changes like defaults and nullable I'm going to start doing it your way.

E

>
>If your dependencies are setup as your application rely on your business object then the business object library would get automatically re-compiled when you rebuild the application. I typically don't re-run the business layer generator after the first time unless I am adding all new business objects. If I add a column to a table, I just go add it then add the property to the entity, and add the parameter row in the DataAccess class. The one I usually forget is to add the parameters and field to the stored procedures also. But then I do not use the partial classes for my code because I really hate keeping track of the business object code in two places. Since I don't re-run the BLG it doesn't cause me any problems.
>Tim