"Jasper Recto" <jrecto99@[EMAIL PROTECTED]
> wrote in message
news:%23ZUb%23NYVJHA.1116@[EMAIL PROTECTED]
>I have a simple table that holds 3 pieces of information:
>
> Part
> ****p Date
> Weight
>
>
> I want to make a form that has a drop down box that the user can select
> the part.
> Then I want it to ask how many containers are they going to enter for
that
> part.
> Then I want it to ask for the weight of each container.
>
> After they press enter, it would populate the table where each container
> weight is a record in the table with the corresponding part number and
> ****p date.
>
> How would I approach this? How can I make a form that will give me X
> amount of fields for the user to put in their weights. The X must equal
> the number of containers the user indicated before.
>
> Once they enter in their information, it must update the table to add X
> amount of records.
>
> What would be a possible approach to this scenario?
Where does the ****pDate come from? Is it Null, to be filled in later, or
is
it also specified on the form?
Can this table contain multiple sets of data for a given part? That is,
if
I open the form, enter a part, and add 3 containers for that part, could I
later, open the form, and add another 7 containers for that part? And if
so, do the original 3 have to be identifiable as one set, while the next 7
have to be identifiable as another set?
Is it essential that no records be added to the table until the user has
provided the weight for each container?
One way I could think of to do this, subject to the answers to my
questions
above, is to add all the necessary records to the table as soon as the
user
has entered the part, the number of containers, and (if appropriate) the
****p date. The weight of all the records added would be Null at this
point.
Then present the records to the user on a continuous subform so that the
user can fill in the weights.
--
Dirk Goldgar, MS Access MVP
www.datagnostics.com
(please reply to the newsgroup)
|
