Help!!!!!!!!!!!!!!!!

akplaygirl

New member
Local time
Today, 02:11
Joined
Feb 19, 2013
Messages
6
I am having the worst time tryingto get a database to work in my favor. So 1st question: how do i make it so i do nOT have to re enter data in every table? most of my tables contain at least one duplicated field from another table. It just seems like a lot of work to have to continually input the same data. 2nd question: what kind of information should my queries consist of? my database is based on employee information 3rd question: Why is it when i try to create multiple keys in a tabe it always omes back that it is a NULL VALUE?
 
1st: Sounds like your tables aren't properly structured. You should store duplicate data, you should link from your tables to another to get that data. Can you post your table structure? Include table names, field names and some sample data.

2nd: Your queries should consist of the information you want to know about. We don't know what you want out of your database. A good way to determine that is to think of your data as a person and ask questions that it would know the answer too.

3rd: I have no idea what you mean. Hopefully posting examples of your data will clear up what you mean.
 
here are a few screenshots of my database. what i ment by my 3rd? was, i went into design view and tried to make a table have 2 keys and when i went to save it access told me my primary key value was NULL and it could not be. What do i need to do to fix this?
as for my queries i guess breakdown birthdays, em contact numbers, evaluation due dates and possibly calculate to let me know when eval time is coming up again. I am also having a issue with one of my current queries. I have attached numerous shots mayb u can help.

thank u
 

Attachments

I have no idea how all those screenshots relate to the issues you initiall posted. So I will just critique the issues I saw:

1. Whats difference between tblEmployeeName, tblEmployeeDetail, tblEmployeeID, tblContacts, tblBirthdayInfo? My guess is you have a lot of overlap among these tables and a few of them could be merged.

2. Vacation table shouldn't have an Employee field and EmployeeID field. You get the name by linking to the table that has the EmployeeID and Name field in it, not by storing redundant data.

3. What's difference between purpose of JobCodeID and JobCode fields in table JobCode?

If you want answers to specific questions, you need to be more detailed in explaining your issues: Post one question at a time, present supporting data (screenshots), tell me how it is occuring. I just can't follow your scattershot of questions and scatter shot of supporting data.
 

Users who are viewing this thread

Back
Top Bottom