Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 2
    Could you tell a thing or two about how a normalized/denormalized database schema could affect the UI/UX? Commented May 2, 2013 at 18:09
  • 1
    One big example would be when you normalize the company. If you toss in a link to a screen with an edit button when you click it, you may very well end up with the secretary screw up I mention further up. One alternative, which is a convenience textfield to rename the company, amounts to the same. The last alternative is to have a dumb text field with no ties to the table at all (just like in Outlook), and to tie things back up in a subsequent (or ajax) screen if there is actual need for normalization. Commented May 2, 2013 at 18:16
  • 1
    I don't get it. Do you mean an Access database? I think no, as (AFAIK) there is no Ajax in Access. Then why couldn't a middle layer (I mean some logic between the frontend and the database) deal with input validation? I know it is not trivial, but it is far from being impossible. Commented May 2, 2013 at 18:24
  • I'm not saying it's impossible. Merely that it's thorny. And that in practice there's very little value in doing so "properly" considering the joins, validation issues, and UI/UX involved, vs something that would actually cover 99% of cases with a conveniently well known UI, aka Outlook. Commented May 2, 2013 at 18:33