>>>James,
>>> Sorry to be dense here, one business object can contain MULTIPLE views?? I see.. What I had envsioned here was since there are many forms in the existing system, most are for generating reports, that when they are removed and have their functionality moved to the menu, there would be a handful of data entry forms.
>>>
>>>One business object would be for the data entry views to handle data, and now I see one business object for the lookups..
>>>
>>>
>>>Does that sound right?
>>>
>>>My manager does have the experience, in Foxpro for Dos and Windows.. He is a sharp guy, but he does so much in theory that he is not seeing the reality of the tools we have..
>>>
>>>Thanks!
>>>
>>>Tony Miller
>>>Seattle City Light
>>
>>Tony,
>>
>>That is feasable... Remember, the general rule is if a view is going to be updated it should get its own business object. If the business object is going to need other views for looking up info (cursors that are intrinsic to the business logic) then include those as well. If you just need a bunch of views for creating reports, use a delogical object. That way you don't incurr the overhead of a full business object.
>
>
>James,
> Is it possible to send you a few questions off the UT, via e-mail??

Keep it on the UT for the benefit of others.