-
If you would like to post, please check out the MrExcel Message Board FAQ and register here. If you forgot your password, you can reset your password.
Multiple entries in one table cell
- Thread starter dpofarre
- Start date
SydneyGeek
MrExcel MVP
- Joined
- Aug 5, 2003
- Messages
- 12,251
Not sure what you mean by this.
(1) Do you want to add, for example, several names to one cell in a table? (2) Or do you want to add different bits of information (city, state, zip) to that cell?
Neither of these are a good idea. Access and other relational systems work on the principle that each record holds a single set of data with a unique "Key" that is related to other bits of data (in other tables) by that Key.
If (1), you may be tracking different events related to one master record (multiple purchases from one customer) -- this is best handled by putting the purchase data into a related table. Then if you need to see all purchases from a single customer, you build a main Customers form with a related Purchases subform. You will see all the related data on the subform.
If (2), this is not a good idea. In databases you should give each piece of information its own column (field) in a row (record). This helps get around issues with mixed data types, but more importantly it makes the information more flexible to use.
Too much information to put into a single post, but look at Microsoft's Knowledge Base http://support.microsoft.com and select Access as the application. In the search area, type Understanding relational design
This will lead to a downloadable tutorial based on the Northwind database that ships with every copy of Office.
Sorry for the long reply, but hope it helps.
Denis
(1) Do you want to add, for example, several names to one cell in a table? (2) Or do you want to add different bits of information (city, state, zip) to that cell?
Neither of these are a good idea. Access and other relational systems work on the principle that each record holds a single set of data with a unique "Key" that is related to other bits of data (in other tables) by that Key.
If (1), you may be tracking different events related to one master record (multiple purchases from one customer) -- this is best handled by putting the purchase data into a related table. Then if you need to see all purchases from a single customer, you build a main Customers form with a related Purchases subform. You will see all the related data on the subform.
If (2), this is not a good idea. In databases you should give each piece of information its own column (field) in a row (record). This helps get around issues with mixed data types, but more importantly it makes the information more flexible to use.
Too much information to put into a single post, but look at Microsoft's Knowledge Base http://support.microsoft.com and select Access as the application. In the search area, type Understanding relational design
This will lead to a downloadable tutorial based on the Northwind database that ships with every copy of Office.
Sorry for the long reply, but hope it helps.
Denis
Upvote
0
Similar threads
- Solved
- Question
