What exactly are you trying to do?
I don't see any foreign keys.
I'm bad at access. I am trying to make a database of all my computers. Those are the tables that I sent before. I'm not sure what is the best way to implement it and how the relationships would go.
At first I was thinking to have every index of every table in the System Information Table to make a relationship but then I wondered if I should just make a field in every table that was the same so that I can just choose what PC Number on each table to represent one PC.
I think I would rename the table, System Information, to tblBox and add to it an FK for each of the other tables.
Advise no spaces or special characters in names. Advise not to use lookup fields in tables. Advise using descriptive names for your PK fields.
I would agree with ItsMe..... but would add:.... Do not use multi-value fields.
Special characters would be like "Model #". Instead use "ModelNum"
You have "ID" as the PK of 9 tables. It would be better to use "MotherboardID", "CPU_ID", "MonitorID", "HardDriveID" (Notice no spaces).
For foreign key fields I would use something like "PCNumber_FK".
If you want to separate words, instead of spaces, use the underscore "_".
I do not see fields for dates. Do you want to know WHEN a monitor was changed? You would need to add a date field.
Cool thanks for the info. What does "FK" stand for. Also, what do you think of my relationships. Is there a better way?I would agree with ItsMe..... but would add:.... Do not use multi-value fields.
Special characters would be like "Model #". Instead use "ModelNum"
You have "ID" as the PK of 9 tables. It would be better to use "MotherboardID", "CPU_ID", "MonitorID", "HardDriveID" (Notice no spaces).
For foreign key fields I would use something like "PCNumber_FK".
If you want to separate words, instead of spaces, use the underscore "_".
I do not see fields for dates. Do you want to know WHEN a monitor was changed? You would need to add a date field.
PK = primary keyWhat does "FK" stand for
FK = foreign key
Better way???? It depends... I don't know your requirements. Are you trying to model a paper process?what do you think of my relationships. Is there a better way?
I don't see anything major wrong with the structure (see above post #6) or the relationships.
Do you really need to track the motherboards? How many times will the motherboards be changed? Same questions for the CPU.
It is up to you to decide what needs to be tracked and how much data you want to enter.....