Hey Tom, I get the sense a lot of 4D dbs are built around the idea you choose a table by starting with an output list form, do some sort of query to narrow down the selection, double click on a record to open it into an input form which may show lists of related records and then you drill down into those. The key thing is all this is taking place in the single window.
My approach has been to make an interface for some aspect of the total 'job' and build lists that relate to that. I work with Orders a lot so I've got several interfaces that provide ways to look at lists of them. 'My List' let's users choose lists of order relevant to them, like in process, quotes, etc. There's also an Order Finder that let's 'em find orders by simple criteria: number, name, address, etc. I even build a popup list of the most recent 10 orders when you right click on a customer name in the 'Partner Picker'. Regardless of where you ask to look at an order it opens a new window, in a new process and displays the order. Unlike the drill-down approach this let's you open several orders at the same time and work with them. Having said all that I don't have any real data on this - just perceptions from conversations. On Wed, Sep 14, 2016 at 12:16 PM, Tom Dillon <[email protected]> wrote: > How different is your interface from the traditional one? > -- Kirk Brooks San Francisco, CA ======================= ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
