Tramp
New member
- Local time
- Today, 11:19
- Joined
- Oct 5, 2004
- Messages
- 5
I recently opened my BIG MOUTH and told my wife i would be happy to try and design a database to help her with inventory control.
While i am still at the very beginning stages of table and structure design, i find myself at an impass right off. A limit of 255 fields per table.
(forgive me if i sound new to all this. I use access nearly every day, but it's all flat file work. I manage mailing and telemarketing lists for a small marketing company, and since we only use "freshly" purchased lists and rarely if ever double back on them, I have had no need to use any more than the "basics")
Here is the scenario: The inventory is of "ITEMS", which are comprised of PARTS. Some "items" may use 4 of one part, and 2 of another. My first thought was to create a table with ITEM# being the pk, and each part# as a field name, with the QTY used listed in each field. The problem is, there are 500+ different part numbers, and access only allows 255 fields. I know there HAS to be a way around this, but like i said, my experience is in flat file work.
While i am still at the very beginning stages of table and structure design, i find myself at an impass right off. A limit of 255 fields per table.
(forgive me if i sound new to all this. I use access nearly every day, but it's all flat file work. I manage mailing and telemarketing lists for a small marketing company, and since we only use "freshly" purchased lists and rarely if ever double back on them, I have had no need to use any more than the "basics")
Here is the scenario: The inventory is of "ITEMS", which are comprised of PARTS. Some "items" may use 4 of one part, and 2 of another. My first thought was to create a table with ITEM# being the pk, and each part# as a field name, with the QTY used listed in each field. The problem is, there are 500+ different part numbers, and access only allows 255 fields. I know there HAS to be a way around this, but like i said, my experience is in flat file work.
I was kinda suspecting a many to many was what i needed. I just never worked with one before. I'll look for the exapmle and learn from that.
