How does the UI, bizobj and database layer in Dabo cope with screens,

business rules and database queries that span multiple tables and

records? Can anyone point me to some example code that shows how Dabo

handles this?

Lots of "models" appear to be somewhat cast in what I call the 1:1:1

syndrome (i.e. each screen holds one record from one table that is

governed by one set of business logic).

How do the layers of dabo handle the (frequent) case where one screen

may have fields (hidden or otherwise) that span multiple tables, thereby

spanning multiple sets of business logic and so on.

... probably clear as mud ...

Thanks,

Michael