Table Relationships

Please solve

  • Recommendation

    Votes: 0 0.0%
  • Alternative

    Votes: 1 100.0%

  • Total voters
    1

mba_110

Registered User.
Local time
Today, 02:16
Joined
Jan 20, 2015
Messages
280
Dear All,

Please i need help in making relationships in attached HR tables data of MS access 2010

Kindly do change the links,fields,name,formats,types etc to meet the requirement of my HR reports.

Thank you very much for your consideration.

kind regards,

MBA
 

Attachments

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
 
A couple of fundamental things with Access and database:

-Don't use a naming convention that uses/allows embedded spaces and/or special characters ('). These will frustrate you with syntax errors. keep it to alphanumeric and underscore(_).
-Start with a list of business rules/specifications that describes -in plain English(non Access/database jargon) of the problem/opportunity to be solved.
-Make a high level data model based on the business rules and refine to a more detailed model.

In general start with the 30,000 foot overview of the issue/opportunity. Make a high level model (pencil and paper is fine). Review the model with the requirement and bounce it off some of the proponents. Revise/clarify requirements and add detail to the evolving model.
Organize some test data and test scenarios and use these to validate the evolving data model. Reconcile every anomaly --adjust the scenarios, business rules, data, test scenario- whichever is causing the anomaly. Repeat until the model matches the requirement. Then, build the database.

It's very akin to building a house -- start with a blueprint or at least an artist's conception.

Good luck
 

Users who are viewing this thread

Back
Top Bottom