It’s up to you not to force on them a seemingly illogical way of working. If you try to persuade database users that they need to input the address first, they'll think you’re mad: in the databases they've ever used, you start with a person’s, or organisation’s, name, and then you proceed to input the address. In my data models, you input an address and then you can assign it to a person or organisation. Personal preferences of authoritative decision makers that must be reflected. There are “who-does-what-and-when-under-whose-authority” rules, for example. Your database needs to sympathetic to these, and operate accordingly. There are things that are unusual, even unique, about how a business operates. Here are some considerations when re-setting your frame of mind from RDBMS engineer to that of a user-interface designer: Business Culture The back end is what the developer considers it should be but the front end must be conceived from the viewpoint of the users. Just as considerable thought goes into data modelling the back-end tables, the same must go into planning the front-end UI objects.
Tables for project management database that’s lead me make a start on this article. It’s the feedback from people who’ve been following the Tips on creating a contacts database,
#Ms access menu examples how to
Guidance for developers on how to design and creation forms as successful user interfaces for Microsoft Access databases.ĭevelopers who are confident in their ability to appreciate the subtleties of RDBMS data modelling, and to engineer the tables and table relationships for the back end of their systems, have contacted me about their lack of experience in designing forms for Access databases. (e) How to Design and Create Forms in Microsoft ® Access
0 kommentar(er)
