By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,336 Members | 2,315 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,336 IT Pros & Developers. It's quick & easy.

How do I make a field with multiple values

P: 3
I am trying to build a database for a list of deals and i dont have much experience with access. Is it ok to just put all the deals in one table. There are only about 6 different fields but there could be up to 1000 deals. One of the fields contains multiple values, how do I set this up.
Any help will be very much appreciated.
Aug 21 '06 #1
Share this Question
Share on Google+
2 Replies


MMcCarthy
Expert Mod 10K+
P: 14,534
The field containing multiple values needs to go into a second table with its own UniqueID Primary Key (Autonumber) and a Foreign Key reference to the Primary Key of the first table.

I am trying to build a database for a list of deals and i dont have much experience with access. Is it ok to just put all the deals in one table. There are only about 6 different fields but there could be up to 1000 deals. One of the fields contains multiple values, how do I set this up.
Any help will be very much appreciated.
Aug 21 '06 #2

100+
P: 179
Each table should be set up with fields pertaining to one subject only. So, the main table will only have info on the client (i.e name, address, city, state, ZIP code, phone number, etc). This table should have a PK set as autonumber (for example, ClientID).

The second table would contain all the info pertaining to the deals made (in which you did not supply any info on). But, for example, if you were selling various items, the second table would be a list of those items. Each record in the table would contain one item only. So, if you sold 2 items to a particular client, that would take up 2 records in the table. In this second table, there would be 2 PKs (one would act as a FK). The first PK would be the same as the PK for the main table (i.e ClientID - even use the same name). The second PK would be a unique identifier for the second table (i.e SalesID)

You then set up a one-to-many relationship between the 2 tables (the main table being the "one" side. You link the 2 tables by the ClientID.

Hope this helps.
comteck
Aug 22 '06 #3

Post your reply

Sign in to post your reply or Sign up for a free account.