Lookup Info and Dump Multiple Fields Into 1 Field

[cpinney1120]

How do I look up several fields from a table and then dump them into one field in another. Please Help!
I want item description and price to go into another table field "Comp1"


NEVER MIND - I JUST FIGURED IT OUT !!!! THANKS ANYWAY!!!!

 

[Kryst51]

How do I look up several fields from a table and then dump them into one field in another. Please Help!
I want item description and price to go into another table field "Comp1"

Good database design would make this unecessary. The two tables should be linked through a relationship, the primary key from the one side of the one-to-many relationship should appear as a foreign key in the many side of the relationship. When you want to view the information together it can be done in forms, queries and reports.

 

[Scooterbug]

Why not just store the ID number of the item into field Comp1? Having the same bit of data in multiple tables isn't the best way to do things.

But, if you want to do that, there are several ways. The easiest way would be an append query.

 

[cpinney1120]

Good database design would make this unecessary. The two tables should be linked through a relationship, the primary key from the one side of the one-to-many relationship should appear as a foreign key in the many side of the relationship. When you want to view the information together it can be done in forms, queries and reports.

Thanks For Your Reply But In this case, I dont want to relate it in a different table. I already have a ton of tables related in the db.

 

[Kryst51]

Thanks For Your Reply But In this case, I dont want to relate it in a different table. I already have a ton of tables related in the db.

Your statement confuses me, because that is how access works, through relationships, it is a relational database, so why would you be concerned about having too many?

 

[Kryst51]

Thanks For Your Reply But In this case, I dont want to relate it in a different table. I already have a ton of tables related in the db.

Actually, the only thing I would be careful of when forming relationships, is to avoid circular relationships...

 

[David R]

cpinney, I caution you against taking the 'easy' way out. The moment you have to change some of that lookup data in your database (change in tax rates, product weights, work hours required for full-time, whatever), you're going to wish you could just go into one table and change one entry.