We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

MS Access: Table development

James Coats
James Coats asked
on
Medium Priority
200 Views
Last Modified: 2012-05-11
In the table "tblToolName" as it suggests will be a list of tool names. We have many tools with the same name such as 6" calipers we currently have about 50 but each has a different serial number.

Do I really need this table? Should I put this field in the table "tblTools" or is it better to leave it like it is??

Measuring-Instruments-3-4-21-11.mdb
Comment
Watch Question

Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Commented:
Try to think about table relationships, one to many, many to many, one to one. One to one is what you would be creating which most of the time are not required... although there may be times when it's usefull! (see the comments on one to one relations on this page: http://msdn.microsoft.com/en-us/library/s780ea06(v=vs.71).aspx)

Commented:
Hold on, I may have been getting this wrong (I had to make assumptions based on the fact there is no sample data and your comment above). If the relationship is:

tblTools.Serial#->tblToolName.ToolName_ID

(which i first assumed) then that would be a one-to-one relationship, however:

tblTools.Tool_Name_FID->tblToolName.ToolName_ID

then it can be one-to-many.

So you could have:

tblToolNames:
ToolName_ID      Tool_Name
1                         6" Caliper

tblTools:
Tool_ID   Tool_Name_FID  Serial_#
1             1                         ABC001
2             1                         ABC002
3             1                         ABC003

etc. That would make the table worth while.

Sorry about the confusion
Gav
James CoatsComputer Info. Sys. Student

Author

Commented:
Thank you for that update I will change it back as I am going to invest a lot of time in this effort.

Commented:
In that case... my 2 cents, I personally would have had a table with a more generic name, say called tblToolType (instead of tblToolName), then you can move other related info such as the 'Type_of_device' field into the one table:

tblToolType
ToolType_ID   Tool_Type   Tool_Name
1                     Measuring  6" Caliper

tblTools
Tool_ID  Tool_Type    Serial_#
1            1                  ABC001
2            1                  ABC002

Hope that helps
Gav
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.