Re: Need some help in data design

From: Tony Toews <ttoews_at_telusplanet.net>
Date: 2000/03/14
Message-ID: <qmnrcsganpeu0pma3jsk6ekgabmr0lssqb_at_4ax.com>#1/1

Kyle Lahnakoski <kyle_at_arcavia.com> wrote:

>One poster suggested a single table, but I am sure that there are some
>attributes that are common to all items. I will suggest two tables.

I would suggest three tables.

>The first will be your standard table:
>
>ItemID | NameOfItem | Vendor | Auction Date | Price
>
>The second will store all those "other" attributes, it corresponds to
>the single table suggestion by the other poster:
>
>AttribID | AttributeName | Value | ItemID

I'd put the Attribute Name in a third lookup table. I have what I call a custom fields setup in many of my apps. Where the attribute name can be anything the customer wants. In my service tracking app it could be license plate, transmission serial number, engine serial number, truck colour, cell phone, cherry picker type, safety inspection date.

Tony

---

Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups.
Microsoft Access Links, Hints, Tips & Accounting Systems at

   http://www.granite.ab.ca/accsmstr.htm VolStar http://www.volstar.com Manage hundreds or

   thousands of volunteers for special events. Received on Tue Mar 14 2000 - 00:00:00 CET