You need three tables at least.
Items in which you have all the candles, holders, etc listed.
Requesitions
Requesition_Items
Why 3 tables? A candle can be order in many different Requesitions and a
Requesition can have many Items like candles. This many-to-many relationship
needs to be broke down into 2 one-to-many relationships.
The Requesition_Items table will store the Requesition number (which is the
primary key field in the Requesitions table and the Item number from the
primary key field in the Items table. That way you can see what was in each
Requesition and an Item (like candles) was in what Requesition.
If the above sounds lie Greek to you (and you aren't Greek!), I highly
recommend getting some relational database training or reading "Database
Design for Mere Mortals" by Hernandez before proceeding any further on this
database.
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
"NAnsar" wrote:
> Hi,
> I am working on a database in which I need to be able to use a cmd button to
> populate a new form but I need to be able to add many records from the
> initial form in order to do so.
>
> for example:
> for lack of a better example I will just make one up that will mock my real
> life database. I have candles of varying degrees of sizes, aromas, colors,
> manufacturers, etc. So each candle has its specified number such as CDL-1248.
> If you open the main form that the data entry occurs to record this data it
> is filled with data relevant to the specified candle. If I am creating a
> requesition to fulfill an order I want to be able to look at the candle
> record, click a command button that dumps the necessary information about the
> candle onto the requesition. I need to be able to find another candle in the
> records and add it to to the same requisition. I am really not sure how to go
> about this. Any help is greatly appreciated.
>
> thank you.
> --
> NAnsar
|
Similar Threads
