>Hi,
>I would like to ask for opinion should I have ALL business object (each link to single table) into single project?
>I am facing problem that, some BOs are in difference project and link to difference table in difference database, but they need to refer to each other.
>
>How could I "categorize" them?

Most of the time my business objects are all in a single project/ dll. I do have a business Object library that is used in 4 different applications, soon to be five. I deploy the same biz obj dll to all of them. Some of those applications only use a smaller subset of the business objects and so I am considering pairing some out into a seperate project but not sure it is worth it. The only real benefit would be I could update the smaller subset and the applications using it without touching the applications that don't. Overall, unless it was really big I doubt it would be worth it.

Anyway, just a data point. If putting them all in one project works for your development and works for your ultimate deployment, then why not.
Oh, by the way I also access three different data sources with my business objects, so it doesn't have to have a bearing on how you seperate them; But it could.
Tim