![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am about to revamp the most referenced table in my whole database and am unsure the best way to approch it. The table's primary key is also used as a part number for all the items in the table. My first problem is that I need to seperate the single part number field into multiple (3 or more). I could make multiple primary key's for each of the new fields, but some would be null, and I hate dealing with multiple primary keys. Plus this change will affect about 50 tables, and countless forms and reports. My thinking is that I need a true primary key, totally seperate from the part number field(s). Maybe an autonumber?? My other problem is "splitting" that part number field. The reason I am splitting is is because there are different "types" of parts and have different part numbering schemes. Other than that ALL the data is the same, and they are referenced throughout the DB exactly the same (same forms, reports, etc... for the most part). So I can't see splitting it up into multiple tables. I want to do this right. Does anyone have any tips or advise? It would be greatly appretiated. Thanks in advance, Jeff |
#3
| |||
| |||
|
|
I am about to revamp the most referenced table in my whole database and am unsure the best way to approch it. The table's primary key is also used as a part number for all the items in the table. My first problem is that I need to seperate the single part number field into multiple (3 or more). I could make multiple primary key's for each of the new fields, but some would be null, and I hate dealing with multiple primary keys. Plus this change will affect about 50 tables, and countless forms and reports. My thinking is that I need a true primary key, totally seperate from the part number field(s). Maybe an autonumber?? My other problem is "splitting" that part number field. The reason I am splitting is is because there are different "types" of parts and have different part numbering schemes. Other than that ALL the data is the same, and they are referenced throughout the DB exactly the same (same forms, reports, etc... for the most part). So I can't see splitting it up into multiple tables. I want to do this right. Does anyone have any tips or advise? It would be greatly appretiated. Thanks in advance, Jeff |
![]() |
| Thread Tools | |
| Display Modes | |
| |