Doug,

PMFJI, but if you load all the cursors in a single business object does that mean that you create a dataenvironment with all three cursors? Are you creating a different data environment for different uses?

I use separate business objects so the requery and refresh are automatic. I even have a combined ComboBoxL and business object for a LookUp object. All I need is to point to the parent business object and the ControlSource and RowSource for the ComboBox.

Just another opinion

Rex

>>As short and sweet as possible.
>>
>>I have a clients form used to add a new client. It has all the usual fields, lastname, firstname age .... I have a clientbizobj that loads the v_clients view dropped on the form. I have 2 listboxes, one for race, one for marital status. These list boxes are based on views from a different database. My question is, should I have one bizobj that loads a dataenvironment with all three views OR should I have 3 bizobjs on the form, one for each listbox and the one for adding a client to v_clients?
>>
>>Thanks
>
>Hi Randy,
>
>I like to separate my views into a separate biz obj. It really gives you more flexibility, but I think the real question is which views will you be adding/deleting/modifying records in? Basically, I use this principal: If I am going to be updating the view, I use a separate biz obj, so that I can use all of the biz obj methods properly for the one view. For example: New(), Save(), Delete(), etc. If the two views are essentially lookups, you can load them with the one biz obj. In this case, it is a matter of whether or not your clientbizobj needs to use those views in order to stand alone. Another way to think about it, if you can instantiate your biz obj outside of the application, and navigate, add, save, update records, then your biz obj is rockin'.
>
>HTH