how to approach repetitive data entry problem

[Guest]

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!

 

[Guest]

I sounds like there are some things that do change from one instance to the
next like start and stop dates, task responsibility, etc.

Try this in the AfterUpdate event:
For each control on the form equate the default to the current value
Me.controlname.Defaultvalue = Me!controlname.value
remember that text defaults must be bracketed by double quote as in
Me.controlname.Defaultvalue = chr(34) & Me!controlname.value & chr(34)

Now when your client indicates a new record, all controls will default to
the last value he entered.

 

[Guest]

Thank you for your suggestion!

yes, actually some fields may/may not change one instance to another as you
pointed out. May be I create some button and indicate that if the proejct is
a big team project, it goes to set the defaults like you suggested, and once
the user wants to stop making the item after, say 30th item, press another
control to go back to the clean main form?

I sounds like there are some things that do change from one instance to the
next like start and stop dates, task responsibility, etc.

Try this in the AfterUpdate event:
For each control on the form equate the default to the current value
Me.controlname.Defaultvalue = Me!controlname.value
remember that text defaults must be bracketed by double quote as in
Me.controlname.Defaultvalue = chr(34) & Me!controlname.value & chr(34)

Now when your client indicates a new record, all controls will default to
the last value he entered.

--
Pictou

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!