ssblue
asked on
Access creating new db - relationships
I am creating a new db and I need some advice and direction on the relationships
Tables:
Info
PIDs
Plants
Tools
Info table will have employee name
PIDs table will have employee PID, First name and Last name
So my question is how do I set this up so I can pick a PID and the Name fill in automatically?
Tables:
Info
PIDs
Plants
Tools
Info table will have employee name
PIDs table will have employee PID, First name and Last name
So my question is how do I set this up so I can pick a PID and the Name fill in automatically?
There is no way for us to help you with the relationships if we do not know what is in the tables (or if they are properly normalized)
For example, ...you say:
What is the purpose of this Info table?
You also say:
Why aren't all of these fields in the same table?
employee name
employee PID
First name
Last name
PID is commonly referenced as a "Field name", not a table name.
So here before we ever talk about "Relationships", ...we need to make sure that your tables are properly "Normalized", ...
So can you take a step back and explain to us what the purpose of this database is?
And also state what data you want the tables to keep track of?
As a start, let's clean up the Employee table:
Table Name: tblEmployees
Fields:
eID (Primary Key)
eFistName
eLastName
JeffCoachman
For example, ...you say:
Info table will have employee nameSo why is the table named "Info", ...instead of "Employees"
What is the purpose of this Info table?
You also say:
PIDs table will have employee PID, First name and Last nameWhat does PID stand for?
Why aren't all of these fields in the same table?
employee name
employee PID
First name
Last name
PID is commonly referenced as a "Field name", not a table name.
So here before we ever talk about "Relationships", ...we need to make sure that your tables are properly "Normalized", ...
So can you take a step back and explain to us what the purpose of this database is?
And also state what data you want the tables to keep track of?
As a start, let's clean up the Employee table:
Table Name: tblEmployees
Fields:
eID (Primary Key)
eFistName
eLastName
JeffCoachman
ASKER
PID is the employee company ID.
The DB is to track the loaning out of tools.
I will need a form which individuals will fill out (paper or online) when taking the tools and then use the same form as a reference when returning the tools. So they will know what they took and what they need to return.
I will also need reports to track what been loaned out, by who, when they took it, when they will return, conditions, etc..
See attachment
Tools-List.accdb
The DB is to track the loaning out of tools.
I will need a form which individuals will fill out (paper or online) when taking the tools and then use the same form as a reference when returning the tools. So they will know what they took and what they need to return.
I will also need reports to track what been loaned out, by who, when they took it, when they will return, conditions, etc..
See attachment
Tools-List.accdb
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was hoping for some dialog on how to build my own not buy someone else's db. These are only free to look at you can't really get into them to see and understand how the relationships, queries and tables are built.
the link I posted is just to show you the forms of the db. you DON"T have to buy it.
as I said above it is FREE,
----open access application then click on Assets and select Lending library
from here you can download the template from Microsoft
you can also view the relationship on this template
as I said above it is FREE,
----open access application then click on Assets and select Lending library
from here you can download the template from Microsoft
you can also view the relationship on this template
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks
Play around with this design (create the relationships)
and add a few records, ...it all should work without forms, ...when you verify that the design is sound, ...thne you can post Questions about the forms and reports
;-)
Jeff
Play around with this design (create the relationships)
and add a few records, ...it all should work without forms, ...when you verify that the design is sound, ...thne you can post Questions about the forms and reports
;-)
Jeff
how do you want to do this? in a form, create a combo box with rowsource from table PID, then use the afterupdate event of the combo to fill the other controls.
describe the other tables purposes in this db, so we can give advice about the relationships needed.