Having only one way for navigating a database application may create problems for the users who prefer other navigation methods over the available one. I try to keep the navigation structure flexible, providing several options to accommodate for different user preferences. Accordingly, an application can contain the following navigation features:
Navigation Assistance Form, Datasheet buttons and the direct access buttons are usually set up so that they leave other user interfaces open, while the Application Map closes all the open user interfaces except the Switchboard. So, when a user finds that he or she has too many user interfaces open, the user can press a shortcut key and open only that user interfaces that is currently needed.
The applications that I put together usually also contain application usage assistance tools and features. The users can learn how to use the application on their own by using its Users Guide. When a shortcut (usually Ctrl+E) is pressed, the Users Guide opens and displays instructions for the currently or most recently displayed used user interface. These features, when combined with training, lead to reduced learning curves, which increase the total value of the application.
Further, user interfaces can also be set up so that all the buttons display messages about their functionality. This feature is a toggle that switches the "button learning mode" on and off.
Additionally, I usually build in features that check the users work and launch warning messages when the application user may be making a mistake, or is about to do something that is not reversible.
My most advanced application usage assistance tools are based on Computer-Optimized Creative Development Method and can, for example, help the application users to do project planning and carry the plans to successful completion. Such tools work equally well regardless of the project type. Other tools based on the same concept provide user interfaces where the user can ask how to perform application usage-related tasks.