Search results

Sara, Yes I think you need the "junction" table. If Applicant "A" wants to apply for postings 1, 2, and 3 then you would have three rows in tblJunction with something like: A, 1 A, 2 A, 3 right ? So the junction table will handle a one to many relationship of one person to many postings. RichM

Chris, Offhand and without any deep analysis, I would not make the "sub" questionnaire number part of a table structure. Even though different people will answer differents subsets of the question domain, your need for analysis capability based on a specific question means you will want to...

Sara, << ooohh! you want to move those fields to tblJunction! I thought you wanted to just put them all in one table. Yeah, I may be able to do that >> Right. When I look at a data model the first question is: "are all these tables really necessary". I think that the 3 tables - junction...

Sara, << I would have to re-enter the applicant's information every time they applied for another position. (name, ssn, address) >> Sorry, don't get that one. I don't see why merging tblApplicants and tblApplication would require any re-entry. I would assume that a row in tblApplicants...

Sara, << I really thought I was doing this right, based on all the stuff I read on normalization in the forum and through web searches and stuff... >> I don't see any normalization problems with the 2 tables. I just don't see any reason WHY you need 2 tables. I don't see any problems if you...

Sara, << One applicant can have many applications, yes. >> Yes that's what the diagram shows. Still don't see what the purpose is. << Each application can apply to one or many postings So if I've applied for three positions this year, I would have three different applications in the junction...

I think that (using a "UNC" path) depends on: 1) the version of Access you are using 2) the version of Windows on the user's desktops 3) the network operating system (assume Novell) I use: Access 97, Windows NT 4.0 workstation, some current Novell stuff. In this combination, I think the "Link...

Sara, << The information for all applicants needs to be the same, whether they are employees or not. >> OK, I understand. So for the process of managing job postings and applicants it looks like you don't need to care much about the tblEmployee and its relationships to other tables. That...

Yes this problem can and often is caused by different drive letter mappings for different users to the same physical drive. //SeverName/Folder/BlahBlah/ can be assingned to the "D:" drive on Dave's desktop, the "E:" drive on Emily's desktop, etc. The solution is to make a common drive letter...

Sara, OK, on with today. You wrote << 1) The database needs to store the SSN and Address of every applicant, whether they are currently employees or not. So should I add these fields to the Employees table? Not every employee applies for other positions, so many records would hold blank fields...

Sara, The picture looks good. A few comments. 1) The big one. I think that tblJunction needs to be linked to both tblEmplolyees and tblApplicants. That's because both employees and non-employees can apply. So you need a common link field OR you have to fake it by putting Employees into...

Sara, << Should I use a lookup from the tblApplicants to the tblEmployees to fill in a TDNo? Then if there is a TDNo, can I get it to fill in the LastName and FrstName fields? And if there isn't a TDNo, the user can fill in the LastName and FrstName fields? So there would be some of the same...

Sara, I think it's OK to keep Employees and Applicants in separate tables. You will want to make a list of all candidates for a Position and that would be easier if all the candidates were in one table. If not then a union query can select common fields from 2 or more tables. RichM (with an h)

Sarah, I think the whole process will be easier if Employees and Applicants can be combined in one table: 1) the additional information for applicants can be stored in a linked table and deleted after a "hire" 2) the table can contain a simple YesNo for "is an employee" Also in the...

Sarah, Trivia questions Does an "applicant" have to be an "employee" ? If no, does an applicant become an employee after they are selected for an open position ? It sounds to me like you want 3 tables: 1) Position 2) Applicant/Employee ? 3) PositionToApplicant The third table...

Matt, You can get the general layout you want with a "cross tab" query. Look into your "Help" from Access or try a search with the key word "crosstab" or "cross" and "tab". RichM

Yes, that's ADO. The path to the back end database can point to a different server than the one that hosts the ASP page. There are some "bug" entries in the Microsoft knowledge base about connecting to databases on remote servers using Novell networks. In general it works. A user who comes to...

You wrote << How safe is to put MS Access database online using ASP with ‘user sessions’? What are the security measures that I should consider just because it is MS Access? >> If you are using an Access data base from an ASP page then normal Access security features don't matter. The Access...

pali, It sounds like: 1 Payment Order is connected to 1 or more Invoices, 1 P O is connected 1 or more Checks The first question is how are Invoices connected to Checks ? Is 1 Check connected to 1 Invoice or to 1 or more Invoices ? You must decide that. If 1 Check is connected to exactly 1...

1) Get everybody out 2) Delete the .LDB 3) Let em back in RichM