N
NES
I have created a contact list/address book in MS Access. The purpose of this
was to separate about 300 names into groups by employment category, and cross
reference them by association with various (and many times multiple)
departments. As devised, it worked as expected. From a Switchboard
(henceforth called a menu) one could select "groups" which then displayed a
sub menu displaying multiple groups per line. Selecting one of these brought
up a sub-sub menu where you could select the specific group to display in the
group form.
Once these names were displayed, one could select a single name, and click a
button called "Details" to display the original data input form for more
details or to allow alteration of the information or cross references by
means of check boxes (for instance if someone appeared in that group that
shouldn't be there, it could be corrected on the spot. Despite the lack of
elegance, it worked like a charm. But the sub-sub menu route seemed complex
for some of our more elderly workers, and I'll admit that it lacked finesse.
BTW, I'm an elderly worker of 63, so no insult was intended. So I changed the
method.
Now, from the main switchboard (menu) clicking on "groups" brings up a FORM
holding a command button for each group. No more sub menus. Clicking on the
button displays the group form as before, and selecting a name and clicking
on "Details" displays the original data input form as before. However,
alterations are now prohibited -- not by an error message -- but just with a
"bleep".
If instead of using the new FORM to select the group form, one uses the
database window to make the selection, and then selects a name from the group
form and clicks on "Details", alterations are allowed as before. It just
isn't working if the new FORM is used to select the group form. This is not
a critical issue, but it is an inconvenience to have to exit the form, go to
the data entry form, search for the name, and then make alterations. I had
hoped to avoid this. Does anyone know why this problem exists. BTW, I'm
working with Office 2003 in Win XP sp 2. Thanks for any help you can give.
Norm Shimmel
Butler, PA.
was to separate about 300 names into groups by employment category, and cross
reference them by association with various (and many times multiple)
departments. As devised, it worked as expected. From a Switchboard
(henceforth called a menu) one could select "groups" which then displayed a
sub menu displaying multiple groups per line. Selecting one of these brought
up a sub-sub menu where you could select the specific group to display in the
group form.
Once these names were displayed, one could select a single name, and click a
button called "Details" to display the original data input form for more
details or to allow alteration of the information or cross references by
means of check boxes (for instance if someone appeared in that group that
shouldn't be there, it could be corrected on the spot. Despite the lack of
elegance, it worked like a charm. But the sub-sub menu route seemed complex
for some of our more elderly workers, and I'll admit that it lacked finesse.
BTW, I'm an elderly worker of 63, so no insult was intended. So I changed the
method.
Now, from the main switchboard (menu) clicking on "groups" brings up a FORM
holding a command button for each group. No more sub menus. Clicking on the
button displays the group form as before, and selecting a name and clicking
on "Details" displays the original data input form as before. However,
alterations are now prohibited -- not by an error message -- but just with a
"bleep".
If instead of using the new FORM to select the group form, one uses the
database window to make the selection, and then selects a name from the group
form and clicks on "Details", alterations are allowed as before. It just
isn't working if the new FORM is used to select the group form. This is not
a critical issue, but it is an inconvenience to have to exit the form, go to
the data entry form, search for the name, and then make alterations. I had
hoped to avoid this. Does anyone know why this problem exists. BTW, I'm
working with Office 2003 in Win XP sp 2. Thanks for any help you can give.
Norm Shimmel
Butler, PA.