Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
coxmg
Starting Member
16 Posts |
 Posted - 2009-07-18 : 11:00:53
|
| I've attached a screenshot of my tables within ACCESS. I'd like to know if the design seems reasonable. The orders table is imported from another system (so the structure of this table is unchageable). The Jewel_Complete_Inventory is a list of unique types of SKUs in stock along with their inventory amount. There is a many-to-many relationship between stones and SKUS. The Stone inventory table contains the unique types of stones and the quantity on hand. Finally, the stone_component table is the linking table between stones and SKUs it contains the quantity of stones within each SKU. Heres a screenshot of the tables:http://create-designs.com/Database_Structure.jpg |
|
|
dportas
Yak Posting Veteran
53 Posts |
Posted - 2009-07-19 : 13:27:37
|
| This is a SQL Server forum. If your question is about Access then you'll probably get more help elsewhere.Regarding the orders table. Have you considered transforming the source data when you import it so that the target structure doesn't have to match the source? A common way to do that is to load data to a "staging" table that matches the source structure and then manipulate it from there into the target structure. Going only on the column names it appears there are some potential problems with the orders table so modifying ought to be to advantage.The Stone_Component table apparently doesn't have a key. I would guess the key ought to be (Style_Num, Stone_ID). |
 |
|
|
|
|
|
ACCESS SQL Table Rview