zebrastripes
Programmer
Hi,
First of all I apologize for this lengthy question. I'm designing a small database for our company. It's basically a database to track recruiting and hiring new employees. I'd like to keep the resumes in the Access database itself (in a memo field). I'm trying to decide whether to put the resumes in the main Employee Candidate table or to break this field out into a new Resume table (which would link back to the Employeee Candidate table).
The main reason I'm concerned about this is when we will be importing data. We're using a third party form processing service to process our web application forms. I'm importing the data from these forms as text files into our Access tables. It complicates the queries for me to have to import into multiple tables (Resume and Employee Candidate as opposed to just Employee Candidate). I'm not a strong sql person in case you didn't already guess.
Sorry about the long-winded question, but we're going to get a fairly high volume of resumes (probably about 150/week)and I already have a large number of fields in this one EmployeeCandidate table). So, I'm wondering if putting this resume field in this table with all the other records will cause the table to reach maximum capacity very soon (at the rate of 150 resumes per week). This fear is the only thing that would cause me to want to put the resume field in a separate table.
Does anyone have any thoughts on this?
Thanks very much,
Zebrastripes
First of all I apologize for this lengthy question. I'm designing a small database for our company. It's basically a database to track recruiting and hiring new employees. I'd like to keep the resumes in the Access database itself (in a memo field). I'm trying to decide whether to put the resumes in the main Employee Candidate table or to break this field out into a new Resume table (which would link back to the Employeee Candidate table).
The main reason I'm concerned about this is when we will be importing data. We're using a third party form processing service to process our web application forms. I'm importing the data from these forms as text files into our Access tables. It complicates the queries for me to have to import into multiple tables (Resume and Employee Candidate as opposed to just Employee Candidate). I'm not a strong sql person in case you didn't already guess.
Sorry about the long-winded question, but we're going to get a fairly high volume of resumes (probably about 150/week)and I already have a large number of fields in this one EmployeeCandidate table). So, I'm wondering if putting this resume field in this table with all the other records will cause the table to reach maximum capacity very soon (at the rate of 150 resumes per week). This fear is the only thing that would cause me to want to put the resume field in a separate table.
Does anyone have any thoughts on this?
Thanks very much,
Zebrastripes