[AccessD] User interface

One technique I often use is to  only have one form visible at any given time to avoid 
accidentally switching between forms.

I keep a stack of form names.

Instead of DoCmd.Openform, I  call a function which:

Accepts a form name and optionally a filter string or open mode.
Pushes the current form's name onto the stack
Hides the current form
Opens the new form.

I have a second function which is called from the On_CLose of each form.
This function Pops the name of the previous form and makes it visible.

I never allow users to access tables directly, but I do let them  double click on a field to tunnel 
down to another data form. I always make the text in the clickable field bold and/or a different 
colour so that they know where they can do that.   That allow me to control whether they can 
only read the data or can modify it.

Combining these two techniques lets users tunnel down through multiple layers of data and 
then back out easily


Another technique I use is to maximize print previews and restore when the preview window 
is closed.

I never use special buttons for navigation/save/delete - I rely on the built in controls. But I do 
have a standard Help template which explains basic Access operations which can be made 
available on F1.


-- 
Stuart 

> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
> Sent: August 27, 2011 9:16 AM To: Access Developers discussion and
> problem solving Subject: [AccessD] User interface
> 
> It has been awhile since I started a new Access project and I am just
> re-examining my user interface techniques and wondering how you guys
> do things.  A good example of this is whether to use buttons
> everywhere such as new record, save etc.  In the past I typically used
> "user training", and the new users are expected to use the record
> selector to go to a new record, do saves by clicking out of the form
> or moving on to a new record etc.
> 
> The specific databases I am working on right now are for people not
> necessarily familiar with a database or data entry and so specific
> buttons can allow icons and control tip text to make things easier to
> learn.  OTOH they take up a lot of room.
> 
> I have written a fairly sophisticated framework that allows me to do
> things like combo double click opening a form to display the data
> table behind the combo.  I have clients who like that, and their users
> are trained on such things, but it is not clear however that in an
> environment where the user is totally unsophisticated, allowing these
> kinds of things is appropriate.  In this case perhaps specific users
> should have this ability but not the general public so to speak.
> 
> What are your thoughts on the user interface.  Feel free to write
> lists of things you do in your user interface.
>