Re: theory and practice: ying and yang

mountain man wrote:

>

>>
>> You then proceed to the claim that the UI can "ride" the table structures
>> and provide complete workability.  That at least is how I term that kind
>> of
>> UI, which our system also implements.  In this system, the menu lists
>> tables.  You work on data in tables, and on the detail screen for each
>> table are hyperlinks to drill down (or up) to child (or parent) tables,
>> with appropriate intelligence making the results of those drill down/ups
>> useful to the user.
>>
>> BUT, you cannot then conclude that this is the "One true UI".

I took this inference from your own site, this page in particular:

http://www.mountainman.com.au/software/southwind/

Where all of the links I looked at showed tabular information. The term "one true UI" is definitely my own characterization of what I thought you were saying, and is probably overly harsh and undeserved.

So perhaps I should fall back to that question: Once the DB is implementing all rules, what is the role of the other layers?

-- 
Kenneth Downs
Secure Data Software, Inc.
(Ken)nneth_at_(Sec)ure(Dat)a(.com)