A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Database Design
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

Multiple subtables



 
 
Thread Tools Display Modes
  #1  
Old May 4th, 2010, 04:48 PM posted to microsoft.public.access.tablesdbdesign
Ernst Guckel
external usenet poster
 
Posts: 50
Default Multiple subtables

Hello,

Not sure how to approach this:

We have an inventory database that has a variety of item types.
Workstations and printers have quite a difference of data fields to be
recorded. Should we store all items in one table and just not use the fields
that do not pertain to those types or should we have a parent table with the
shared fields and multiple subtables to store the specific fields to each
type?

The second sounds like a better idea but couldnt things go wrong later with
multiple tables linking to the same parent table?

Thanks,
Ernst.
  #2  
Old May 4th, 2010, 05:58 PM posted to microsoft.public.access.tablesdbdesign
KARL DEWEY
external usenet poster
 
Posts: 10,767
Default Multiple subtables

Do an analysis on which fields to include in the main table based on how many
times a given field would be used or not.
I think using one other table instead of multiple subtables to store the
specific fields to each type having these fields --
tblSubInfo --
SubInfoID - primary key
InventoryID - foreign key
DataType -
Data -

DataType tells you what the data is (serial, price, color, etc.).

--
Build a little, test a little.


"Ernst Guckel" wrote:

Hello,

Not sure how to approach this:

We have an inventory database that has a variety of item types.
Workstations and printers have quite a difference of data fields to be
recorded. Should we store all items in one table and just not use the fields
that do not pertain to those types or should we have a parent table with the
shared fields and multiple subtables to store the specific fields to each
type?

The second sounds like a better idea but couldnt things go wrong later with
multiple tables linking to the same parent table?

Thanks,
Ernst.

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 04:40 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.