Thank you for your input and reference links.
>UI should have no concept of tablename. It should not know where the data is coming from. It should make a request to get a record by customer number, where it passes just the customer number or all customers in a certain state, where it passes just the state. Then an XML record set gets sent from the DA through the BIZ and then to the UI.
>
>Some places for info:
>
http://www.jamesbooth.com/weblayersi.htm>
http://www.jamesbooth.com/n-tier.htm>See "Class based data management" at
http://www.tightlinecomputers.com/Downloads.htm>
>>I am working on a 3-tier framework. UI (VFP form), BIZ, and DA will have bunch of properties of the same name. E.g. TABLE_NAME.
>>
>>The value of a property will be set in the UI tier (property of VFP) form. E.g. property TABLE_NAME will have value "MYTABLE".
>>
>>When UI form is instantiated I need to make sure that BIZ and DA properties of the same name get the same values.
>>
>>The way I instantiate tiers is as following:
>>
>>INIT method of UI form instantiates BIZ class (and references to a property of UI form).
>>INIT method of BIZ class instantiates DA class (and references to a property of a BIZ class).
>>
>>I can set properties of BIZ class in the INIT of the UI form. But if I set properties of DA class in the INIT of BIZ class it will be too late.
>>
>>I am looking for suggestions, please.
>>
>>Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham