I have a field that records whether an Employee is permanent or
temporary. My thought was to simply have 1 field that if checked means
that the employee is a permanent hire as opposed to an unchecked box
which means that person is a temporary employee.
Does anyone have any feedback on how this plays out with the end-user?
Thanks,
Tim
On Nov 13, 10:08 am, tbrog...@gmail.com wrote:
> I have a field that records whether an Employee is permanent or
> temporary. My thought was to simply have 1 field that if checked means
> that the employee is a permanent hire as opposed to an unchecked box
> which means that person is a temporary employee.
>
> Does anyone have any feedback on how this plays out with the end-user?
>
> Thanks,
>
> Tim
Hello Tim. There is an option in the table design that allows you to
set the field to a "Yes/No" field. You can then link this field to
whatever form you currently have and it will allow the user to only
check yes/no.
Hope this helps!
Dorothy
financialreporting@googlegroups.com
Hi Dorothy,
Yes. I do know about the Yes/No fields. I realized after I posted that
my question might not have been perfectly clear.
I was thinking of using a checkbox instead of a Yes/No only because I
was thinking that it might be easier to deal with the data on the
backend.
And I guess what I'm really after is, whatever type of control I use
what is the best layout of the control(s) on the form from a user's
perspective stylistically?
What do you think?
Tim
On Tue, 13 Nov 2007 11:20:49 -0800, tbrogdon@gmail.com wrote:
>Yes. I do know about the Yes/No fields. I realized after I posted that
>my question might not have been perfectly clear.
>I was thinking of using a checkbox instead of a Yes/No only because I
>was thinking that it might be easier to deal with the data on the
>backend.
>And I guess what I'm really after is, whatever type of control I use
>what is the best layout of the control(s) on the form from a user's
>perspective stylistically?
>What do you think?
What the field's underlying "style" is, is somewhat questionable. You
really shouldn't be applying styles at the table level, even though
Access allows it. Indeed, users should *never* be able to open a
table directly!
As for on a form, feel free to use a combobox, list, option group,
toggle, or checkbox as you feel fit.
Personally, I tend to use comboboxes, as they are re-sizable and
captionable in ways the checkboxes aren't.
Please Post Any Replies To This Message Back To the Newsgroup.
There are "Lurkers" around who can benefit by our exchange!
Again I find myself mis-communicating.
My question is - for ease of use for the end-user and for the cleanest
data entry and any subsequent programming issues that may come up -
does anyone have an opinion as to what might be the most efficient and
cleanest way for me to present the question to my end-users?
Thanks,
Tim
On Nov 13, 10:30 pm, tbrog...@gmail.com wrote:
> Again I find myself mis-communicating.
>
> My question is - for ease of use for the end-user and for the cleanest
> data entry and any subsequent programming issues that may come up -
> does anyone have an opinion as to what might be the most efficient and
> cleanest way for me to present the question to my end-users?
I use checkbox for booleans. Sometimes, in addition, when I want the
user to be very aware about some condition, I change the background
color of the (single-record) form, say green for permanent, yellow for
temporary.
Thanks Lyle. That's exactly the kind of mental "jog" I was looking
for. I was also thinking about the field values "incorrectly" as well.
I am going to make it easy on myself and just have the one field -
HireStatus and will only have 2 permissible values - Permanent or
Temporary and my form can then be a combobox and that is that! :-)
Sometimes I just need to hear it from somebody else!
Thanks,
Tim
An added consideration is that now you can know if the user actually
selected a value (it would be empty if they did not) as opposed to
"Forgot" to mark the value.
Sort of the reverse can come up on option groups. I will sometimes
allow for a none of the above choice since once an entry is checked in
an option box you cannot uncheck it and the user may have hit the
choice by accident.
Ron
tbrogdon@gmail.com wrote:
> I have a field that records whether an Employee is permanent or
> temporary. My thought was to simply have 1 field that if checked means
> that the employee is a permanent hire as opposed to an unchecked box
> which means that person is a temporary employee.
>
> Does anyone have any feedback on how this plays out with the end-user?
>
> Thanks,
>
> Tim
>
You could make it a combo with an underlying Yes/No field. If the field
name was PT, you could make a two column combo (hide first column) with
values. Ex:
-1;"Perm";0;"Temp"
I think the users will understand a more verbose obtion.
news:1195011059.761997.82140@o3g2000hsb.googlegroups.com...
> Again I find myself mis-communicating.
>
> My question is - for ease of use for the end-user and for the cleanest
> data entry and any subsequent programming issues that may come up -
> does anyone have an opinion as to what might be the most efficient and
> cleanest way for me to present the question to my end-users?
It is really a matter of the style with which your users, and you, are more
comfortable. If it is truly a Yes/No, and you can choose a default, then
any of Radio (Option) Button, Check Box, Toggle Button, List Box, Combo Box,
or even Text Box can work. As Lyle does, I usually use a Check Box or an
Option Button, but in specific cases, have used some of the others.
I'd particularly use a Combo Box if I thought that sometime in the future,
there might be more than two options for this, for example, if you add
"contractor" or "part-time regular employee" or "full-time temporary", you
won't have to go back and change the UI... just add them to the table.
Larry Linson
Microsoft Access MVP
>
> I'd particularly use a Combo Box if I thought that sometime in the future,
> there might be more than two options for this, for example, if you add
> "contractor" or "part-time regular employee" or "full-time temporary", you
> won't have to go back and change the UI... just add them to the table.
>
> Larry Linson
> Microsoft Access MVP
You make a really good point. We have fairly high turnover and I don't
want to delete any records because all production is tied directly to
employee so a combo box does seem the better option with a "No longer
with the company" option - and of course any of the other
possibilities that you point out.
Thanks,
Tim