Mick,

>For the first time I have a situation, that is a little different than I've had before in the .NET world. I have a table of sites with a SiteID. This field will be used through the rest of my tables as a way to limit all the activates to happening with that one site. My question is in two parts. How do the rest of you add a new column through all your BOs, do you use the Business Layer Generator and bite the bullet and make changes as needed, or do you just add the new field by hand through the classes?
>
>Next, this is essentially a global property. How do the rest of you handle this sort of thing? I'm not asking for exact details just overall best practices.
>
The Business Layer Generator lets you regenerate just the entity object if you want. If you have defaults that need to be set, regenerate that also. If you havn't coded any specific rules, then you can regenerate that also. That is how I do it unless I have created my own code in the defaults or rules classes then I add to them manually. I rarely put any hand code in the entity object. Of course, you can easily add a column to the entity object by hand also. Not really a big deal.
Tim