Results 1 to 3 of 3
  1. #1
    Ant_Snell is offline Competent Performer
    Windows 10 Office 365
    Join Date
    Jul 2021
    Location
    UK
    Posts
    118

    One or two tables of similar data

    I am just requesting a bit of advice on pros & cons re design. I am doing a DB with employee information table’s ( Name, DOB, Address, Qualifications etc.) I want to also include information for job applicants. Many of the details would be exactly the same as an applicant may well become an employee. I am unsure if it would be better to have an applicant table, with status’s say: Applicant, interviewed, job offered, rejected etc. then append all the details into an employee table if the applicant joins the company. Or just have one table including applicants and employees but then filter records via queries to only show employees or applicants depending on requirements. Re pros and cons, I am thinking in the terms of speed potentially having a table full of applicants who never got past interview stage ( I will obviously purge old details periodically for GDPR reasons).




    Thanks for your comments

  2. #2
    CJ_London is offline VIP
    Windows 10 Access 2010 32bit
    Join Date
    Mar 2015
    Posts
    11,397
    Really think it is a matter of personal choice. Using a single table simplifies forms since you only need the one form, but then additional filtering work. Or two forms and additional work transferring data. Re performance, with proper indexing, should not make a significant difference.

    You mention a qualifications field - I would expect this to be in a separate child table since employees/applicants could have more than one qualification. Same with status - I would have that in a separate table as an applicant could apply for more than one job. Status could also hold the value for 'employed' or 'role' if they are employed. Include a date field and that will tell you when an applicant applied, was accepted/rejected or an employee changed role

  3. #3
    Ant_Snell is offline Competent Performer
    Windows 10 Office 365
    Join Date
    Jul 2021
    Location
    UK
    Posts
    118
    Thanks Ajax
    re the child tables, yes the both the employee table and the applicant table (should I do one) would have many related child tables, I was just trying to make the question concise without to much detail. I am leaning towards separate tables for employees & applicants at this stage but was just interested in people’s views.

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Getting similar data from two tables
    By wheddingsjr in forum Access
    Replies: 15
    Last Post: 02-28-2018, 07:17 PM
  2. Replies: 2
    Last Post: 04-26-2016, 05:24 PM
  3. Replies: 3
    Last Post: 03-18-2015, 09:24 AM
  4. Replies: 2
    Last Post: 11-18-2014, 01:27 PM
  5. Relating Multipe Tables With Similar Data To A Master Table
    By TotalChaos in forum Database Design
    Replies: 1
    Last Post: 04-13-2013, 12:57 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums