Francisco,

>hello people, i dev 2 databases (app datatabase and workflow database), now i have a object called library in workflow database but this object need the users of the app database, the wrong way (i think) is use a view directly in this business object because library reside in workflow database not in app database, i wrong?. in case only need use 1 time the list user the only is using a business object for this work?, or i can another way?>

In most object-oriented problems there are usually multiple solutions with some having only a slight advantage or no advantage over others. Theh final solution you choose may simply boil down to a matter of style.

Not knowing the full scope of your application and the problem that you are solving makes it difficult to recommend the best course of action. You can definitely make a case for creating a User business object that returns information regarding system users...in reality the location of the data is transparent to the outside world. Only the business object's data access component needs to know its physical location.

But, this is also true if you don't create a separate business object and do a simple lookup from within your business object (a view, SQL passthrough, etc.)...the location of the data wouldn't be the deciding factor on whether I would choose to create a separate business object or not.

Personally, I tend to create different objects to handle different types of entity data...a User business object for user data, an Invoice object for invoice data, etc.

Regards,