Sorry but using SBT for your primary data you need a union to combine 2 identical tables of data that are separate for some stupid SBT reason 10 years ago. Those tables are Current and History. They appear for every major database in SBT. SOTRAN has SOYTRN SOMAST has SOYMST and the list goes on.....
It's pretty stupid but they just do it.
So I need a Union to find shipped orders that are in my current database as well as shipped ones in my history file. But more to the point, All the orders are visible insted of having the user know when the order was created
and the user can get more data when they want it.
I agree with the monster syndrome you state below. I am leaning more in the method/style that you are commenting on.
__Stephen Russell
Memphis FPUG
>>Now what business object do I use for a multi page (3) look up business object. Page 1 is a text box to get the Customer's Number from a view of all customers. Page 2 is an open orders grid. Page 3 is a shipped grid. From each of those pages there will be command buttons that display more detail as needed by the operator.
>>
>
>It sounds like you don't need to have the view be a union. You should have seperate views, one for the open orders, one for the shipped orders.
>
>Or, you could have a view of the views.... if they are read only.
>
>>As you can see this form set is a monseter. Only data entry will be done via Shipped orders, all others are just grids for display.
>>
>
>You can create seperate forms that you call to display these grids... that way, the initial form is not so heavy... Also, you can programatically create a window and use the browse command, if you just want to show read only data this may be a better way to go.
>
>BOb
