HOW do I make selections and carry only those selections thru proc

Hello,

I hope someone can help me with this. THANK YOU in advance for any and all
tips and advice.



I have many tables. The ones that I think are pertinent to this issue are....

tblPOTODO
PART_NO
MANUF1
MANUF1_PN
MANUF2
MANUF2_PN
MANUF3
MANUF3_PN

which represents the part number and 3 possible manufactures of the part and
their respective part numbers.


tblVENDOR
VENDORNAME
ADDRESS
PHONE
FAX
VENDORNO

which lists the vendors that we use


tblMANUF
MANUF
VENDORNAME
VENDORNO

which lists the manufactures that each vendor carries. In this table,
manufacturers are listed multiple times because more than one vendor carries
each manufacturer AND vendors are listed multiple times because vendors carry
multiple manufacturers.

For example, a manuf001 part may be sold by vendor01, vendor 02 and vendor 03.
Additionally, vendor01 may carry parts by manuf001, manuf002 and manuf003.




so, if I have a part number with the following info. (and that part number
is in tblPOTODO)

(our) PART_NO: 1234-5678
MANUF1: manuf001
MANUF1_PN: abc001
MANUF2: manuf002
MANUF2_PN: lmn001
MANUF3: manuf003
MANUF3_PN: xyz001


What I need to do is create a form, or some other format (if there is a
better way than a form) to have my user CHOOSE a manufacturer from the 3
listed as possible options. Once they choose a manufacturer, then I need to
look at my tblMANUF to see which vendor supports that product and give them
those vendor choices (this very likely will be more than 3 options, could be
many vendors)... so that they can select which vendor to purchase this part
from. All of this information needs to be written to tblPOTODO, which is the
table that my Purchase Order gets it's information from.



Thank you so much for your help!

On Feb 4, 3:14*pm, kealaz wrote:
Hello,

I hope someone can help me with this. *THANK YOU in advance for any and all
tips and advice.

I have many tables. *The ones that I think are pertinent to this issue are....

tblPOTODO
* * * * PART_NO
* * * * MANUF1
* * * * MANUF1_PN
* * * * MANUF2
* * * * MANUF2_PN
* * * * MANUF3
* * * * MANUF3_PN

which represents the part number and 3 possible manufactures of the part and
their respective part numbers.

tblVENDOR
* * * * VENDORNAME
* * * * ADDRESS
* * * * PHONE
* * * * FAX
* * * * VENDORNO

which lists the vendors that we use

tblMANUF
* * * * MANUF
* * * * VENDORNAME
* * * * VENDORNO

which lists the manufactures that each vendor carries. *In this table,
manufacturers are listed multiple times because more than one vendor carries
each manufacturer AND vendors are listed multiple times because vendors carry
multiple manufacturers.

For example, a manuf001 part may be sold by vendor01, vendor 02 and vendor 03.
Additionally, vendor01 may carry parts by manuf001, manuf002 and manuf003..

so, if I have a part number with the following info. (and that part number
is in tblPOTODO)

(our) PART_NO: *1234-5678
* * * *MANUF1: *manuf001
* * MANUF1_PN: *abc001
* * * *MANUF2: *manuf002
* * MANUF2_PN: *lmn001
* * * *MANUF3: *manuf003
* * MANUF3_PN: *xyz001

What I need to do is create a form, or some other format (if there is a
better way than a form) to have my user CHOOSE a manufacturer from the 3
listed as possible options. *Once they choose a manufacturer, then I need to
look at my tblMANUF to see which vendor supports that product and give them
those vendor choices (this very likely will be more than 3 options, could be
many vendors)... so that they can select which vendor to purchase this part
from. *All of this information needs to be written to tblPOTODO, which is the
table that my Purchase Order gets it's information from.

Thank you so much for your help!

Parts
--------
PartNo_Internal (how you refer to a part)
PartDescription

ManufacturesParts
=========
ManufacturerPartNo
PartNo_Internal (FK to Parts)
ManufacturerID


Manufacturer
------------------
ManufacturerID (PK)
ManufName
....

I'm so sorry! All that background information and I didn't clarify WHAT my
question is.

What would be the best way to capture the selections (information) and carry
that on to my ultimate destination, which would be tblBUY (not tblPOTODO as
stated in the original post; oops!).

tblBUY
PART_NO
VENDORNAME
MANUF
MANUF_PN

which is the final information after all of the selections have been made.

Can I do this with a form? If so, how would the users make the selections?
Which controls would be best suited for this application. Once the
Manufacturer is selected, can I have them make another selection for the
vendor, based on their first selection? The vendor list, would be different
depeneding on which manufacturer is selected. If there is a better way to do
this, other than a form, like a query, or other.... please let me know also.

Thanks!

You need one-to-many relationship as shown by Piet Linden.

--
KARL DEWEY
Build a little - Test a little


"kealaz" wrote:

I'm so sorry! All that background information and I didn't clarify WHAT my
question is.

What would be the best way to capture the selections (information) and carry
that on to my ultimate destination, which would be tblBUY (not tblPOTODO as
stated in the original post; oops!).

tblBUY
PART_NO
VENDORNAME
MANUF
MANUF_PN

which is the final information after all of the selections have been made.

Can I do this with a form? If so, how would the users make the selections?
Which controls would be best suited for this application. Once the
Manufacturer is selected, can I have them make another selection for the
vendor, based on their first selection? The vendor list, would be different
depeneding on which manufacturer is selected. If there is a better way to do
this, other than a form, like a query, or other.... please let me know also.

Thanks!

Okay, once I have that one-to-many relationship set up, then what? How do I
get present the selections so that they can be made by the end user?

Thanks.



"KARL DEWEY" wrote:

You need one-to-many relationship as shown by Piet Linden.

--
KARL DEWEY
Build a little - Test a little


"kealaz" wrote:

I'm so sorry! All that background information and I didn't clarify WHAT my
question is.

What would be the best way to capture the selections (information) and carry
that on to my ultimate destination, which would be tblBUY (not tblPOTODO as
stated in the original post; oops!).

tblBUY
PART_NO
VENDORNAME
MANUF
MANUF_PN

which is the final information after all of the selections have been made.

Can I do this with a form? If so, how would the users make the selections?
Which controls would be best suited for this application. Once the
Manufacturer is selected, can I have them make another selection for the
vendor, based on their first selection? The vendor list, would be different
depeneding on which manufacturer is selected. If there is a better way to do
this, other than a form, like a query, or other.... please let me know also.

Thanks!

Use form/subform with Master/Child links set on the common fields that relate
the tables.
--
KARL DEWEY
Build a little - Test a little


"kealaz" wrote:

Okay, once I have that one-to-many relationship set up, then what? How do I
get present the selections so that they can be made by the end user?

Thanks.



"KARL DEWEY" wrote:

You need one-to-many relationship as shown by Piet Linden.

--
KARL DEWEY
Build a little - Test a little


"kealaz" wrote:

I'm so sorry! All that background information and I didn't clarify WHAT my
question is.

What would be the best way to capture the selections (information) and carry
that on to my ultimate destination, which would be tblBUY (not tblPOTODO as
stated in the original post; oops!).

tblBUY
PART_NO
VENDORNAME
MANUF
MANUF_PN

which is the final information after all of the selections have been made.

Can I do this with a form? If so, how would the users make the selections?
Which controls would be best suited for this application. Once the
Manufacturer is selected, can I have them make another selection for the
vendor, based on their first selection? The vendor list, would be different
depeneding on which manufacturer is selected. If there is a better way to do
this, other than a form, like a query, or other.... please let me know also.

Thanks!