Good answer! That was where I was heading. But...

I don't like the idea of polluting the interface of the business object with methods to support a specific UI control. This leads me to consider a seperate business object for the control.

I don't like this because I see business objects as simulatons of real world objects and this UI control is purely implementation detail. Also the control only needs readonly access to the data and a bizobj seems too heavy for the task.

Doctor My Eyes

jMM

>Dr. Miller,
>
>>I have a control that needs to have it's own encapsulated data access. Meaning that the control needs to perform some data access necessary to the proper functioning of the control that has no bearing on, and should be invisible to, all other controls and the form.
>
>How about instantiating a private instance of the business object for this control?
>
>Regards,