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 |
|
dsetzer
Starting Member
31 Posts |
 Posted - 2001-02-17 : 23:03:57
|
| I am in the process of designing an application that will allow us to sell a multitude of products (ranging from printed materials to medical product samples to clothing wear and even as far as electronic files for purchase).The easy part is, I need to come up with a central items table that will contain the CORE information: itemID, client Item #, description, inventory level, pack size, category, image file, preview imageThe part I am struggling with is the Item Details table(s) that I need to store specific information about each type of item we have. For example:- printed materials: we need to know printing specifications (this paper, this ink, this binding)- product samples (hazardous material, usage, notes)- clothing (type, sizes available, colors available)- electronic files (type of file, file size)We are trying to design the product so that if someone comes along and wants to store another type of product in the database, it is flexible enough that it could all be done through data entry by customer service.I can handle the front-end coding and probably the Stored Procs for the data retrieval, but, I can't come to terms with what the table structures should be.Any help in the form of posts, reading material, informational websites is greatly appreciated. |
|
|
|
|
|
|
|
Database Structure - Item Table