Tables Relationships & Design

[mba_110]

Dear All,

I need help in making relationships and design for attached HR Tables.

Kindly modify,change format and do the relationships as per requirement.

i need this to be in order

thanks & regards,

MBA

[orange]

Cross posted http://www.access-programmers.co.uk/....php?p=1406745

Readers can not provide detail comments on your database because:

-you have not told us WHAT the data base is about(WHAT is the Business you are trying to support)
-you have not provided any Business Rules to help identify tables or relationships

Please provide a 5-6 line description of a typical day in the business.
Here is a sample of the level of detail required, and this is where you start.

Narrative (from RogersAccess Library)
ZYX Laboratories requires an employee tracking database. They want to track information about employees, the employee's job history, and their certifications. Employee information includes first name, middle initial, last name, social security number, address, city, state, zip, home phone, cell phone, email address. Job history would include job title, job description, pay grade, pay range, salary, and date of promotion. For certifications, they want certification type and date achieved.
An employee can have multiple jobs over time, (ie, Analyst, Sr. Analyst, QA Administrator). Employees can also earn certifications necessary for their job.

[mba_110]

Dear All,

Sorry for any inconvinence caused to you all.

I have posted this in other forums to expedite the result, however I need to explain that I am doing a HR database that includes list of employees working in company and their diffrent entitlement reports based on their employment contracts and calculation method.

It's involve many logical and methamitical formulas but that will be asked once design, tables data and relationships done properly.

I hope it has clear explaination furthermore you can open and check by yourself to see what I am trying to carryout this is my first project and I am eager to achieve this.

Thanks & regards.

MBA

[June7]

Suggest you work through tutorials at http://www.rogersaccesslibrary.com/.

Create links in Relationships builder.

Advise not to use spaces and special characters/punctuation (underscore is exception) in naming convention. Names like No's Tickets (p,a) will be troublesome and frustrating.

[ssanfu]

In addition to June's comments, I would suggest that you do not use "look up FIELDS" or calculated fields in your tables.

The Ten Commandments of Access
http://access.mvps.org/access/tencommandments.htm

The Evils of Lookup Fields in Tables
http://access.mvps.org/access/lookupfields.htm



You have used Text fields as your PK fields. Here is info about Primary keys:

Microsoft Access Tables: Primary Key Tips and Techniques
http://www.fmsinc.com/free/newtips/primarykey.asp

Autonumbers--What they are NOT and What They Are
http://www.utteraccess.com/wiki/index.php/Autonumbers

Use Autonumbers properly
http://access.mvps.org/access/general/gen0025.htm

All of my PK fields are autonumber type fields.