Search

[DevAccess]

Hello

I have one developed one database wherein I have done one to many relationship, please see attached screenshot for the same.

In this database user can enter N number of certifications for given candidates.


Now I would like to have search functionality wherein user can select Certification(s), Education(s). and Postion(s) from listbox.

this result should bring Name of Candidate who had selected certification and all other certifications has been selected for him and same for Positions and Education(s).

So for example if selected certifications has been match into the database it should return all the educations, certis and positions related to him.

even if second certis which has been selected for him/her is belongs to the first result we found then this should be discarded.

 

[Uncle Gizmo]

Were you drunk or half asleep when you wrote that! All joking aside, I think the information is there but I'm having an awful job ferreting it out. Could you have another go at posting your question?

 

[DevAccess]

Were you drunk or half asleep when you wrote that! All joking aside, I think the information is there but I'm having an awful job ferreting it out. Could you have another go at posting your question?

hahahahah lol


Sorry Uncle Gizmo for my bed English.

What I want to convey is that I have one to many relationship between Candidate and Certification/Educations/Positions

Now in Search there would be three list box namely Education, Certis & Positions which would be filled up using details entered by user in above fields while they create resume record.

Now question...

Given three search criteria as above, How to retrieve a Candidate's all Certi, Education & Positions records ?

 

[BeeJayEff]

please see attached screenshot for the same.

That screenshot doesn't help me at all. How about a screenshot of your Relationships ?

 

[jdraw]

How about describing what you are trying to accomplish in plain, simple English - no jargon - just as you would tell an 8 yr old?
Forget listbox etc and use plain English, until users understand your requirement.

 

[DevAccess]

How about describing what you are trying to accomplish in plain, simple English - no jargon - just as you would tell an 8 yr old?
Forget listbox etc and use plain English, until users understand your requirement.

Here is the attached relationship diagram.

What I want is when user is presented list of choices to be selected from education, certifications & Positions. I want to get Candidate Name and their all the information like Eudcations, Ceritification & Positions.

We would give the choice select user to educations, certis, and positions on search form when they hit search form I would like to have find all the persons matching certis or Positions or Educations.

I wanted to build resume based on this in word document, one word doc for each users and their certifications, educations, Positions.

I hope this is clear now.

 

[BeeJayEff]

First a few comments from what I can see so far :

1. Do not use CandidateName as a PKey, use CandidateId or similar - what happens when you have two John Smiths to consider ?
2. Remove all spaces from field names - use underscores or camel case, as you have done for the table names
3. Correct spelling mistakes in field names (might seem trivial but can save lots of wasted effort later)
4. Better not to have compound primary keys (also unnecessary)
5. How would you handle a candidate who had worked for the same CompanyName for two or more distinct periods ?
6. I might expect to see separate tables for Companies, Certifications, Degrees, SecurityClearances, LabourCategories - but that's your shout.

No more time at the moment.

 

[DevAccess]

First a few comments from what I can see so far :

1. Do not use CandidateName as a PKey, use CandidateId or similar - what happens when you have two John Smiths to consider ?
2. Remove all spaces from field names - use underscores or camel case, as you have done for the table names
3. Correct spelling mistakes in field names (might seem trivial but can save lots of wasted effort later)
4. Better not to have compound primary keys (also unnecessary)
5. How would you handle a candidate who had worked for the same CompanyName for two or more distinct periods ?
6. I might expect to see separate tables for Companies, Certifications, Degrees, SecurityClearances, LabourCategories - but that's your shout.

No more time at the moment.

Thanks, I did as per your say.

My questions, Can I build a view wherein in one line I can see all the information related to one person/candidate in one row ?

Or since it is one to many it will have different row ? for each certification and each education record ?