How to Avoid Confusing User

  • Thread starter Thread starter S Jackson
  • Start date Start date
S

S Jackson

I need some advice on how to set up a couple of forms so that I don't
confuse my users.

I have a table with about 500+ entries for employees. Some of the fields in
the table include:
SurveyorID
SvyFirstName
SvyLastName
SvyTitle
SvyEmploy (yes/no - employee is no longer employed with agency)

In the SvyTitle field, the user enters the employee's title. Some of the
employees will have the title of "program manager." I have built a main
form where cascading combo boxes help the user pick a "program manager" for
that case/record. But, how do I set it up when:

a. An employee is promoted to "program manager" and the employee table
hasn't been updated; or
b. A new employee is hired as a "program manager" and needs to be added
to the employee table?

And, the user would have to find the employee who was the former program
manager and update the record to reflect that this employee is no longer
with the agency.

Please understand that I am NOT asking how to code things, because I think I
can figure that part out. What I am asking is how to set up the proper
steps for the user to do this housekeeping to avoid confusing them. I
thought I would start with a button on my main form that says: "Add/Edit
program managers." But, then what? How do I guide the user through this
process? My biggest concern is setting this up to avoid a user entering an
employee twice (a situation where an employee has been promoted, for
example). Anyone have any examples of how they have handled similar
situations?

TIA
S. Jackson
 
I need some advice on how to set up a couple of forms so that I don't
confuse my users.
.......
Click to expand...
Please understand that I am NOT asking how to code things, because I think I
can figure that part out. What I am asking is how to set up the proper
steps for the user to do this housekeeping to avoid confusing them. I
thought I would start with a button on my main form that says: "Add/Edit
program managers." But, then what? How do I guide the user through this
process? My biggest concern is setting this up to avoid a user entering an
employee twice (a situation where an employee has been promoted, for
example). Anyone have any examples of how they have handled similar
situations?
Click to expand...

Ask the user how he/she would like it.
If I am doing such thing, I first scratch a form and the I go to the
user and let them play with it. Most of the time my logic is different
then the user's, because i know what's underneath the form and I react
with database logic. The user mostly has a total different aproach.

If you expect an answer to a personal mail, add the word "manfred" to the first 10 lines in the message
MW
 
Back
Top