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  

Parts Database Table Design



 
 
Thread Tools Display Modes
  #1  
Old February 28th, 2005, 05:39 AM
John Floyd
external usenet poster
 
Posts: n/a
Default Parts Database Table Design

I need to create a parts database to be able to lookup parts for different
machines. The problem I am having is trying to determine how to 'break-down'
the machines so that the parts can be found. I want to be able to use a drop
down list to select a machine name, then an area of the machine, then an
assembly, ect.
Two problems:
1- Some of the machines are small machines and do not need to be
'broken-down' as much in order to find a specific part or list of parts. For
example, One of the machines only reqires a machine name and sub-assembly to
find the part I would need. Another larger machine would require machine
name, area, assembly, sub-assembly and possibly more break-down to find a
specific part.
2- I would like to incorperate a drop down list of machine names, areas,
assemblies, sub-assemblies, ect. to eliminate the possibility of user error
when entering, or extracting, information. The problem I have is how to
link, for example, an assembly name to a specific area of a specific machine
when the same assembly name may or may not be used in another machine.
Thank you for any help or guidance you can provide.
  #2  
Old February 28th, 2005, 09:53 PM
Graham Mandeno
external usenet poster
 
Posts: n/a
Default

Hi John

Have you considered using a TreeView control, instead of individual combo
boxes?

Your hierarchy of "Units" could be represented by a single table, with
fields as follows:
UnitID (autonumber primary key)
UnitName
UnitType (a code representing machine/area/assembly/etc)
ParentID (the UnitID of the "containing" unit)

If each part is used only once, then your parts table can have a field for
the UnitID of the containing Unit.

Otherwise, as is more likely, if parts can be used in multiple assemblies,
you will need a junction table to represent the many-to-many relationship
between units and parts:
PartID
UnitID

--
Good Luck!

Graham Mandeno [Access MVP]
Auckland, New Zealand


"John Floyd" John wrote in message
...
I need to create a parts database to be able to lookup parts for different
machines. The problem I am having is trying to determine how to
'break-down'
the machines so that the parts can be found. I want to be able to use a
drop
down list to select a machine name, then an area of the machine, then an
assembly, ect.
Two problems:
1- Some of the machines are small machines and do not need to be
'broken-down' as much in order to find a specific part or list of parts.
For
example, One of the machines only reqires a machine name and sub-assembly
to
find the part I would need. Another larger machine would require machine
name, area, assembly, sub-assembly and possibly more break-down to find a
specific part.
2- I would like to incorperate a drop down list of machine names, areas,
assemblies, sub-assemblies, ect. to eliminate the possibility of user
error
when entering, or extracting, information. The problem I have is how to
link, for example, an assembly name to a specific area of a specific
machine
when the same assembly name may or may not be used in another machine.
Thank you for any help or guidance you can provide.



 




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

Similar Threads
Thread Thread Starter Forum Replies Last Post
using a form parameters to open a report jkendrick75 Setting Up & Running Reports 5 January 14th, 2005 05:05 PM
Get data from combo box to popluate the next box Lin Light Using Forms 4 December 30th, 2004 05:01 PM
Update - If statement Dan @BCBS Running & Setting Up Queries 13 December 14th, 2004 06:02 PM
Access 2000, autonumber fields Zyberg74 General Discussion 3 November 17th, 2004 04:24 PM
Here's a shocker Mike Labosh General Discussion 2 October 26th, 2004 05:04 PM


All times are GMT +1. The time now is 09:13 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.