Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi all! We have been experiencing an issue on site where threads have been missing the latest postings. The platform host Vanilla are working on this issue. A workaround that has been used by some is to navigate back from 1 to 10+ pages to re-sync the thread and this will then show the latest posts. Thanks, Mike.
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Access problems

  • 13-07-2006 11:03am
    #1
    Skud
    Registered Users, Registered Users 2 Posts: 1,821 ✭✭✭


    Hey i got a database in access and having problems with the relationships. Heres what I got, 2 tables: Jobs and Applicants (This contains 3 columns so that if an applicant applied for more than one job it should be linked) The problem is its having trouble with 2 things. The jobs are linked by job id. So if an applicant applies for more than one job it's not really linking properly.

    and 2 is if u click the + next to the applicant to see the job it is linked to this does not work if it is entered via the applicants table. But it works only in the applicants table for the first job... (if that made any sense to you then you'll understand).

    The jobid is primary key in the jobs table so this shouldnt matter. I just could be using the 1:N relationships wrong.


Comments

  • #2
    bonkey
    Registered Users, Registered Users 2 Posts: 15,443 ✭✭✭✭bonkey


    Jobs / Applicants is typically an N:N relationship, not a 1:N

    Each Job can have multiple applicants, each applicant can apply for multiple jobs.

    You typically need an intermediate table which is "JobApplicant".


  • #3
    mountainyman
    Closed Accounts Posts: 2,268 ✭✭✭mountainyman


    What bonkey said.

    Effectively you need an applicant details table which would contain the JOB ID
    and the APPLICANT ID.

    Each job can have more than one applicant.
    Each applicant can apply for more than one job.

    So you need to create a table where APP ID is unique and JOB ID is unique.

    Northwind has a couple of examples.

    MM


Advertisement