Re: how to approach repetitive data entry problem

Dave

Your description focuses on "how" ... how to make a form do something.

In Access, it all starts with the data. Are you saying that your table has
"about 50 switch" fields and "about 13 engineer" fields? If so, this is the
kind of design you'd expect ... in a spread***! You won't get the best
use of Access' relationally-oriented features and functions if you insist on
feeding it '*** data.

Please step back from the form for a moment and describe, in more detail,
how your data is structured.

Regards

Jeff Boyce
Microsoft Office/Access MVP

"dave" <dave@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9D872490-D22C-4BDB-A5C8-D1E094C972FC@xxxxxxxxxxxxxxxx
hello,

I have a [PROJECT] table that has
-projectName
-description
-region
-List of Switches (there about 50 switches)
-engineer (about 13 engineers)
-Start date

fields.
I have no problem creating an item in this table in a form. But I just
found
out another requirement for the form.

What my supervisor wants to be able to do, is that he sometimes gets a big
project that is deployed nationwide. and he has to create 50 different
items
- that is, while the project name and description remain constant, there
could be 40 or 50+ switches that are affected by this project so He wants
to
be able to create this project for each switch, so basically 50+
projects(with the same name) and with EASE. He doesn't want to open the
form
50 times and copy paste everything.

he needs 50 individual project items in there because some engineers
complete the project, some has to be chased down. Also, they may have
different due dates, deliverables etc.. Based on the same project, but
different engineer. So it needs to create upto 50 projects (1 per switch)
if
it's an area wide deployment.

Any suggestion as to how I should approach this?
onlything i could think of was maybe using parent-child form, where child
has a continuous form, and somehow create a macro to auto populate some of
the fields.

Thank you for your time experts!


.