If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
interview questions
7) Q: Given a new project, how would you go about developing it.?
A: Again, there is no one right answer here, but the answer they give will tell you whether they've actually ever developed a database. One thing I look for is an indication they sit down and develop their table structure *first*. Table design is third Business Rules are first Logical Data design is second -- Dave Hargis, Microsoft Access MVP "Roger Carlson" wrote: Well, I'll give it a go. To me, the most important thing is that they understand database DESIGN. Access as an application generator is easy enough to learn on their own if they have a good understanding of table design. Design your tables right, and you have an easy time with your app. Design them wrong, and you are constantly creating work-arounds to fix things that should have been done right the first time. Several questions I use: 1) Q: What is a Primary Key. A: It is a special kind of index whose value cannot be Null and must be unique for each record. Primary keys can be either single fields or composed of multiple fields. If composed of multiple fields, it is still a single primary key. There is no such thing as multiple primary keys in a table. 2) Q: Should an Autonumber field be used as a Primary Key? Why or why not? A: There is no single correct answer for this, but I listen for the reasoning. Opinions vary on this topic, but if they say No, they'd better have a pretty convincing answer for me. In most cases, autonumber fields make perfectly good primary keys. However, I know experienced developers (including MVPs) who do not advocate autonumber fields for primary keys. Valid reasons, IMO, include the fact that autonumber field sometimes get confused and assign values previously assigned, and a primary key in Access creates a clustered index, which may not be the best indexing scheme for your table. Invalid reasons are dogmatic like: "my college prof said to only use natural keys". 3) Q: How do you define Relationships in Access? A: Relationships are defined in the Relationship window by clicking a dragging the primay key field of one table to the corresponding foreign key of another table. The Referential Integrity checkbox MUST be clicked, although the Cascade options do not. Note: I've had people proudly tell me that they never use the Relationship Window or never set up Referential Integrity. If you don't do those things, you don't HAVE relationships and are not using the power of a relational database. 4) Q: What is a one-to-many relationship? A: This is where a single record in a table is related to one or more records in another table based on a primary-key/foreign-key. 5) Q: How do you create a Many-to-Many relationship in Access? A: You cannot create a M:M relationship directly in Access. You must first create a "linking" table (it can be called other things as well), which has as foreign keys, the primary keys of the other two tables. Then you create a One-to-Many relationship between each of the tables and the linking table where the linking table is on the "many" side of both. 6) Q: What is Normalization? A: Normalization is a methodology or process for removing as much redundant data from the database as possible, while at the same time insuring that the data will be able to be reassembled as needed. There are many stages of normalization (call Normal Forms). Most developers agree that the minimum level of normalization is the Third Normal Form (3NF) and that level is acceptable for most database applications. Note: Many people may not have a text-book definition of normalization memorized, but have a pretty firm grasp of how to create a normalized database. 7) Q: Given a new project, how would you go about developing it.? A: Again, there is no one right answer here, but the answer they give will tell you whether they've actually ever developed a database. One thing I look for is an indication they sit down and develop their table structure *first*. There are no doubt more, and you could ask a LOT more about Access specifically, but these questions, to me, are key to whether the person either can develop (or can be trained to develop) Access database applications. -- --Roger Carlson MS Access MVP www.rogersaccesslibrary.com "G" wrote in message ... I know this is 'off the wall'. I have to come up with a couple interview questions for a client to determine if an applicant is qualified technically to do the job in ACCESS. The task will be to combine several databases and datasources into one usable database. Preferably with a frontend/backend. Do any of you have any suggested questions that you would pose to an applicant? -- Thank you in advance for your assistance. It is greatly appreciated. |
#12
|
|||
|
|||
interview questions
You started one of those threads that exites a lot of people. But, to answer
your question, Roger gave some decent advice. Also, there are companies that provide technical testing in multiple disiplines. Sorry I can't tell you who they are, but a couple of times I have had to take them. The Access evaluation I took was very thorough. You would have to know Access very well to be able to get a good score. -- Dave Hargis, Microsoft Access MVP "G" wrote: I know this is 'off the wall'. I have to come up with a couple interview questions for a client to determine if an applicant is qualified technically to do the job in ACCESS. The task will be to combine several databases and datasources into one usable database. Preferably with a frontend/backend. Do any of you have any suggested questions that you would pose to an applicant? -- Thank you in advance for your assistance. It is greatly appreciated. |
#13
|
|||
|
|||
interview questions
Also TIC
-- Dave Hargis, Microsoft Access MVP "Jamie Collins" wrote: On Dec 14, 2:43 pm, mscertified wrote: I know this is 'off the wall'. I have to come up with a couple interview questions for a client to determine if an applicant is qualified technically to do the job in ACCESS. I think you need more than a 'couple of questions'. I'd suggest more like 15-20. And there is not much point in us suggesting questions unless you know the answers too. TIC: Don't forget the 'qualitative' ones e.g. Q. What would you name a table that models anything you like here? A. anything they like here so long as the first three letters are tbl. Depends on the language. In spanish it would be mes Q. An Access database has a TEXT column that is constrained by validation rule to be one of three possible values, the widest being 17 characters. What is the defined width of the column as seen in Table Design view? A. 50 characters wide. Depends on whether I looked at it before I changed it. Good to mess with you again, Jamie etc etc Jamie. -- |
#14
|
|||
|
|||
interview questions
"Klatuu" wrote: You started one of those threads that exites a lot of people. But, to answer your question, Roger gave some decent advice. Allow me to elaborate on a reply I gave to Roger directly (he didn't reply to me: I guess I didn't get the job, too much of a smart arse, wouldn't fit in, fair enough g). In the UK if the interviewee requests it we are required to provide the interview questions (including technical assessment questions) and how the interviewers assessed the candidate based on the answers given; they can ask for all documentation relating to their application, including any notes (and doodles g) that may get taken down during the interview. So if Roger's notes say, "I rate the answer as incorrect because they didn't check the RI box when creating an Access Relationship" then the interviewee could argue the toss (we're hiring geeks, remember g) that they *did* give a correct answer because the question as stated did not ask for RI. I'm guessing that Roger only ever uses Access Relationship with RI enforced, thus forget that "Access Relationship" has a meaning much more vague than RI implies e.g. the former can be based on columns of differing data types whereas the latter requires the same data type and a unique constraint (again guessing that Roger's are always based on PKs rather than UNQIUEs). And here's my point: if you ask objective question to which you think you know the answer, aren't you merely trying to hire someone with a subset of your (or your technical expert's) knowledge? Call me an optimist but I wouldn't mind end up with someone who will bring new knowledge to the team (you know the old chestnut, "Aim to be the least experienced person in the room" etc). I find subjective questions to be more revealing e.g. "here's a scenario, what would you approach be?" That question should kick off a discussion lasting half an hour or more, which is good but if you have limited time at least aim for something where there isn't one correct answer e.g. calendar table or a UDF (or something else) to calculate holidays? For a collection class's container object what are the relative pros/cons of an array, VBA.Collection, Dictionary object and fabricated ADO recordset? (any other candidate objects?) For the objective questions, give them a pen and paper and get them to write some code (VBA, SQL, etc). If using a GUI is acceptable, print off some screen shot and get them to mimic mouse clicks, drag and drop, etc with a pencil e.g. they click a menu button and you switch the paper to show the appropriate screen etc. Jamie. -- |
#15
|
|||
|
|||
interview questions
Although not an interview question, the principle would apply to a technical
test question I was had to take as the final exam for a course on a radio transmitter. The instructor had told us there would be only one question on the exam. The question was: Completely describe the APS-36. -- Dave Hargis, Microsoft Access MVP "Jamie Collins" wrote: "Klatuu" wrote: You started one of those threads that exites a lot of people. But, to answer your question, Roger gave some decent advice. Allow me to elaborate on a reply I gave to Roger directly (he didn't reply to me: I guess I didn't get the job, too much of a smart arse, wouldn't fit in, fair enough g). In the UK if the interviewee requests it we are required to provide the interview questions (including technical assessment questions) and how the interviewers assessed the candidate based on the answers given; they can ask for all documentation relating to their application, including any notes (and doodles g) that may get taken down during the interview. So if Roger's notes say, "I rate the answer as incorrect because they didn't check the RI box when creating an Access Relationship" then the interviewee could argue the toss (we're hiring geeks, remember g) that they *did* give a correct answer because the question as stated did not ask for RI. I'm guessing that Roger only ever uses Access Relationship with RI enforced, thus forget that "Access Relationship" has a meaning much more vague than RI implies e.g. the former can be based on columns of differing data types whereas the latter requires the same data type and a unique constraint (again guessing that Roger's are always based on PKs rather than UNQIUEs). And here's my point: if you ask objective question to which you think you know the answer, aren't you merely trying to hire someone with a subset of your (or your technical expert's) knowledge? Call me an optimist but I wouldn't mind end up with someone who will bring new knowledge to the team (you know the old chestnut, "Aim to be the least experienced person in the room" etc). I find subjective questions to be more revealing e.g. "here's a scenario, what would you approach be?" That question should kick off a discussion lasting half an hour or more, which is good but if you have limited time at least aim for something where there isn't one correct answer e.g. calendar table or a UDF (or something else) to calculate holidays? For a collection class's container object what are the relative pros/cons of an array, VBA.Collection, Dictionary object and fabricated ADO recordset? (any other candidate objects?) For the objective questions, give them a pen and paper and get them to write some code (VBA, SQL, etc). If using a GUI is acceptable, print off some screen shot and get them to mimic mouse clicks, drag and drop, etc with a pencil e.g. they click a menu button and you switch the paper to show the appropriate screen etc. Jamie. -- |
#16
|
|||
|
|||
interview questions
On Dec 17, 3:34 pm, Klatuu wrote:
Although not an interview question, the principle would apply to a technical test question I was had to take as the final exam for a course on a radio transmitter. The instructor had told us there would be only one question on the exam. The question was: Completely describe the APS-36. I presume this is the equivalent of, "Completely describe the Microsoft Jet Engine." [PS I'm still waiting for my copy of the documentation e.g. details such as this -- http://msdn2.microsoft.com/en-us/lib...4(SQL.80).aspx -- but for Jet. It must exist, who has it...?] Jamie. -- |
#17
|
|||
|
|||
interview questions
Yes
-- Dave Hargis, Microsoft Access MVP "Jamie Collins" wrote: On Dec 17, 3:34 pm, Klatuu wrote: Although not an interview question, the principle would apply to a technical test question I was had to take as the final exam for a course on a radio transmitter. The instructor had told us there would be only one question on the exam. The question was: Completely describe the APS-36. I presume this is the equivalent of, "Completely describe the Microsoft Jet Engine." [PS I'm still waiting for my copy of the documentation e.g. details such as this -- http://msdn2.microsoft.com/en-us/lib...4(SQL.80).aspx -- but for Jet. It must exist, who has it...?] Jamie. -- |
#18
|
|||
|
|||
interview questions
Actually, I had no idea you had replied to my answer as I've long since put
you on my Block Senders list. You are always more interested in picking nits than answering the original poster's question. Not sure how you got through this time. Oh well, add it again. Certainly there are different answers. I thought I made it clear (though perhaps I did not) that I was more interested in the reasoning behind the answer than specific "correct" answers. Creating relationships in Access via a SQL statement is, of course, legitimate, and if someone gave that anwser, I would certainly know a great deal about their abilities. (However, I would also wonder why they would choose to use a SQL statement when they have a perfectly good UI option available.) The real purpose of that question is to ascertain that the interviewee knows 1) what relationships are and 2) how to create them. Too often I've interviewed candidates who said: "What's a relationship?" or "Oh, I never use them. I create them in the queries." -- --Roger Carlson MS Access MVP www.rogersaccesslibrary.com "Jamie Collins" wrote in message ... Allow me to elaborate on a reply I gave to Roger directly (he didn't reply to me: I guess I didn't get the job, too much of a smart arse, wouldn't fit in, fair enough g)... |
#19
|
|||
|
|||
interview questions
On Dec 18, 2:49 pm, "Roger Carlson"
wrote: You are always more interested in picking nits than answering the original poster's question. I was not trying to be rude but on refelction I see I made my point at your expense for which I apologize. I was trying to stress the importance of the wording of your questions and answers. I'm sorry to hear that you feel that is nit picking but, again, I stress that the topic here is about hiring *geeks* i.e. the kind of people who are interested in the fine detail. I would also wonder why they would choose to use a SQL statement when they have a perfectly good UI option available Don't just wonder, ask! And stick around to here the answer; perhaps we'll all learn something I think your "perfectly good" assessment of the UI is ill founded. Continuing the Relationships example, how do you create a "fast foreign key" (see http://support.microsoft.com/kb/275561) or use the SET NULL referential action (same article) using the UI? ALTER TABLE tblInvoices ADD CONSTRAINT FK_tblInvoices FOREIGN KEY NO INDEX (CustomerID) REFERENCES tblCustomers (CustomerID) ON UPDATE CASCADE ON DELETE SET NULL; Jamie. -- |
#20
|
|||
|
|||
interview questions
I would like to thank all of you who responded to this question. You all gave
excellent answers. The final questions I submitted were as follows: Question: List the steps necessary to design a database. Question: Name two analysis tools used in ACCESS Question: Describe normalization Question: What is the maximum size for an ACCESS database and what happens when you exceed that size? What can you do to prevent this and what are your options if you do exceed the maximum limit? Question: Your task is to import data from another source, like Excel or a Text File. This needs to be done on a regular basis and is very detailed. What tool would you use in ACCESS to automate this: Question: Can you use nested If-Then-Else statements in a query? Question: Describe when the OnPrint property occurs and give an example of when you used this property I provided the answers to the non-technical interviewer. Again, Thanks to all of you for your input! -- Thank you in advance for your assistance. It is greatly appreciated. "G" wrote: I know this is 'off the wall'. I have to come up with a couple interview questions for a client to determine if an applicant is qualified technically to do the job in ACCESS. The task will be to combine several databases and datasources into one usable database. Preferably with a frontend/backend. Do any of you have any suggested questions that you would pose to an applicant? -- Thank you in advance for your assistance. It is greatly appreciated. |
|
Thread Tools | |
Display Modes | |
|
|