Advice

S

Stockwell43

Hello,

I have a question pertaining to the number of field on a form. A manager has
55 tasks that she wants her staff to tick mark. Am I able to put this many on
a form and have it function properly? All that will be entered is a number in
each field on a daily basis.

Thanks!!!
 
S

Stockwell43

Hi Chris,

No, it should only be 1-3 digits in each field. All the fields may not be
filled in each day may be only half. Would that still fit ok?

Thanks!
 
J

Jeff Boyce

You are asking a question about "how", but "how" depends on "what".

Are you saying that your underlying table will have those (55) tasks as
individual (?Yes/No?) fields? If so, you've mistaken Access for a
spreadsheet!

More info, please...

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
S

Stockwell43

Hi Jeff,

I am saying I would have 55 task on the form and each task (depending on the
day) the user will enter a number. So if they 15 credit tickets for the day,
they would put in 15 for that task and so on. I did this with a lower amount
of task like maybe 15 but not this many and manager said she does not want to
consolidate any of them.
 
J

John W. Vinson

Hello,

I have a question pertaining to the number of field on a form. A manager has
55 tasks that she wants her staff to tick mark. Am I able to put this many on
a form and have it function properly? All that will be entered is a number in
each field on a daily basis.

Thanks!!!
Click to expand...

Chris is right that you can easily have 55 controls on a form... BUT!!!!

Storing these tasks as 55 yes/no fields in a table *is simply wrong design*,
if that's what you were planning to do. What if two new tasks are defined? Do
you need to redesign your table, redesign your form, all your queries, all
your reports just to add a task? OUCH!

A table of Staff, a (55 row now, maybe more later) table of Tasks, and a table
of Assignments with one row per person per task per day is a much better
design; and a form with a subform or with a multiselect listbox and some code
to populate the table will be a much better approach than a hard to read form
with a mass of checkboxes.
 
S

Stockwell43

Hi John,

As I explained to Jeff, There are NO checkboxes. All of the staff might work
any of these 55 tasks on any given day. They are only enter a number, NO
checkboxes. How would it be if I put a CBO with the users names and a date
field. Then put a subform in the main form with all the tasks and a field to
enter their volume worked. This way, they can select the tasks they worked
versus having a whole form full of tasks?

But then, If I use the Tasks ID field to link the main and sub forms
together, How would I pull the information out on the query, would it be the
same as if it were one form? I don't have much experience with subforms.

Thanks John!!
 
J

Jeff Boyce

Sorry, I still don't have enough of a sense of what data is being stored in
the tables to offer informed suggestions about the form you are using.

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
A

Arvin Meyer [MVP]

I would use an unbound form, pre-filled with each task from a task table.
Once the data is ready to be submitted, a button would write only those rows
that have a filled in value to the detail table. Now, you have both
convenience, and a normalized structure.
 
J

John W. Vinson

Hi John,

As I explained to Jeff, There are NO checkboxes. All of the staff might work
any of these 55 tasks on any given day. They are only enter a number, NO
checkboxes. How would it be if I put a CBO with the users names and a date
field. Then put a subform in the main form with all the tasks and a field to
enter their volume worked. This way, they can select the tasks they worked
versus having a whole form full of tasks?

But then, If I use the Tasks ID field to link the main and sub forms
together, How would I pull the information out on the query, would it be the
same as if it were one form? I don't have much experience with subforms.
Click to expand...

I'm still not totally clear on how you want this to work, but might this work?
You would have three tables:

Staff
StaffID <primary key>
LastName
FirstName
<etc>

Tasks
TaskID
TaskName

Worklist
StaffID <link to Staff, who did the work>
TaskID <link to Tasks, what they did>
WorkDate <Date/Time, when they did it>
Volume <how much they did>

You could use a Form based on Staff, wherein the user would select their name
from an unbound combo box to navigate to their record; and a subform to update
Worklist. The Master/Child Link Field would be the StaffID, there'd be a
textbox for Workdate defaulting to Date(), and a textbox for Volume.

If each person will be doing only a rather small subset of the tasks, it would
be simple to just put a combo box on the subform bound to TaskID to select the
task. If they'll routinely do some work on most or all of the tasks, you could
base the subform on a Query left-joining the Tasks table to the Worklist
table; this would show all 55 records (or more, if you add tasks), and the
user could enter values into the Volume field to automatically create a record
for that task.
 
Top