Difference between revisions of "Microsoft Access Front End"
(Created page with '== General == The front end of an application is the only way for a user to manipulate data. == Accessibility == The front end usually offers the following measures of accessibi...') |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:Microsoft Access]] | ||
| + | [[Category:Architecture]] | ||
== General == | == General == | ||
The front end of an application is the only way for a user to manipulate data. | The front end of an application is the only way for a user to manipulate data. | ||
| Line 8: | Line 10: | ||
It is possible to provide the whole functionality in a single front end, while in larger systems it is wise to follow the "one task, one front end" paradigm, which means that all forms and the underlying business logic is bundled in one front end for each task. | It is possible to provide the whole functionality in a single front end, while in larger systems it is wise to follow the "one task, one front end" paradigm, which means that all forms and the underlying business logic is bundled in one front end for each task. | ||
| − | The navigation is facilitated my providing | + | The navigation is facilitated my providing one but not limited to one of the following: |
| − | * | + | * menue |
| − | * | + | * toolbar |
| − | * | + | * shortcut |
| + | * ribbon (since Microsoft Office 2007) | ||
| + | |||
| + | While ribbons are considered as user friendly by some users, it needs a more complex setup (XML and VBA). | ||
=== Key Bindings === | === Key Bindings === | ||
| Line 31: | Line 36: | ||
The user interface can be tightened and simplified further by disallowing to show the database window, disabling the Microsoft Access special keys, namely F11 and Alt+F11 amongst others. Converting the front end into a compiled version (.mde), protecting the code and digitally signing the code project adds additional security. | The user interface can be tightened and simplified further by disallowing to show the database window, disabling the Microsoft Access special keys, namely F11 and Alt+F11 amongst others. Converting the front end into a compiled version (.mde), protecting the code and digitally signing the code project adds additional security. | ||
| + | When writing code for a MDE version of the database, please keep in mind that this requires - as the code is completely inaccessible - much more effort, care and accurateness in the code itself; writing a lot of error handling routines, for example, is a very time consuming and error-prone task and might lead in addition to a lot of code corrections in the beginning. | ||
== Startup == | == Startup == | ||
| Line 44: | Line 50: | ||
* Messages | * Messages | ||
* Task List | * Task List | ||
| + | |||
| + | The user login should not be realized through an Microsoft Access System Database (mdw), as the options are limited with this solution, the handling is cumbesome and last but not least this feature is considered as deprecated since latest version of Microsoft Access. | ||
=== Logging === | === Logging === | ||
Latest revision as of 15:51, 15 July 2010
General
The front end of an application is the only way for a user to manipulate data.
Accessibility
The front end usually offers the following measures of accessibility:
It is possible to provide the whole functionality in a single front end, while in larger systems it is wise to follow the "one task, one front end" paradigm, which means that all forms and the underlying business logic is bundled in one front end for each task.
The navigation is facilitated my providing one but not limited to one of the following:
- menue
- toolbar
- shortcut
- ribbon (since Microsoft Office 2007)
While ribbons are considered as user friendly by some users, it needs a more complex setup (XML and VBA).
Key Bindings
The key bindings throughout the front end must be consistent and should accelerate the typical usage of the front end. This encompasses
- navigation and
- usage
Menues
The menues provide the most traditional way of offering functionality. They can be used for
- navigation and
- initiating actions
Depending on the complexity of the user operations and the design of the user interfaces, context menues can be a good choice too.
Tool Bars
Tool bars provide a more visual kind of offering functionality to a user. They offer navigational and functional accessibility but must not be overloaded by too much functionality.
User Interface
The user interface can be tightened and simplified further by disallowing to show the database window, disabling the Microsoft Access special keys, namely F11 and Alt+F11 amongst others. Converting the front end into a compiled version (.mde), protecting the code and digitally signing the code project adds additional security.
When writing code for a MDE version of the database, please keep in mind that this requires - as the code is completely inaccessible - much more effort, care and accurateness in the code itself; writing a lot of error handling routines, for example, is a very time consuming and error-prone task and might lead in addition to a lot of code corrections in the beginning.
Startup
Sanity Checks
- References
Auto Start / Auto Exec
- Default settings
User Login
- Access Control Lists
- Messages
- Task List
The user login should not be realized through an Microsoft Access System Database (mdw), as the options are limited with this solution, the handling is cumbesome and last but not least this feature is considered as deprecated since latest version of Microsoft Access.
Logging
- Log in / log out
Timer
- Log out active users on demand
Maintenance
- Compact and repair back end databases
- Back up back end databases
- Update data by SQL statements
- Update front ends
- Run automated tasks like
- fetching data
- sending mails
- running external automated tasks
Usage
User Forms
User forms are provided for all main tasks of the front end.