Apr 21 2005, 11:35 AM
im trying to integrate a small survey into my existing database. Which means im sharing the STAFFNAMES table for the survey.
I have 7 questions on a form, each question givin 3 options. like so
Do i need a table for each Q?
Which would be the best way to do this?
Apr 21 2005, 11:59 AM
RespondentID (PK and auto)
QuestionID (PK and auto)
AnswerID (PK and auto)
ResponsesID (PK and auto)
Something like the above should get you started...
Apr 23 2005, 11:18 AM
i have the questions in one table and answers in another table as you have shown. BUT I just dont know how i could lay out the questions on a form to fill up the junction table.
I thought I wouldnt need the questions table because if im using Option Groups on the forms.
any help would be apprecited.
thanx for the help.
Apr 23 2005, 11:25 AM
I have to leave right now and I will be gone the rest of the day, but I have attached a demo that should answer your questions..
Apr 24 2005, 11:56 AM
the demo was ok. Im just getting used to VB.
But I just cant use the login part. because I already have a table with all the <employee> data. Is there another method, a simpler way how I can input the data into the junction table. I have tried various combinations. It just keeps giving me referential integrity problems.
Any suggestions would be appreciated.
Thank you for the demo.
Apr 25 2005, 10:42 AM
I don't understand the problem. At some point you are going to have to select a user to take the survey. The current demo is set up so that the same person cannot take the survery twice. To use the 'Login' form you only need to base the combo box on your existing table of employees so they can select their name and do the survey.... All the surveys that I have seen have used a form of some type to sign in the user and then let them take the survey...
Apr 26 2005, 11:49 AM
Im still struggling with the demo u posted.
I have a bit confusion about the UserId and EmployeeID fields.
In my existing EMPLOYEE table(where I have all usernames) I already have an <employeeID> field. Do I need another field labeled UserID and if I do where should it be? and whats its purpose?
hope you will help me out.
any suggestions will be appreciated.
thanx again for all the assistance
Apr 26 2005, 03:05 PM
In the demo I sent you there is a table called tblEmployes. In that table is a field called UserID. For your purposes wherever you see UserID substitute your EmployeeID for UserID. This is the only place you have to change the name as EmployeeID is used everywhere else in the program. I did not realize this until just this moment so I will change my demo, but all the other tables should work for you if you use your EmployeeID and disregard the UserID.
I'm sorry about the confusion with the demo, but you should be ok now...
Apr 28 2005, 07:34 AM
I just couldn't get past the login part.
I think im stuck with the append query in your demo.
Will it be possible for you to revise the demo and post it AGAIN so that there is no swapping of UserID and EmployeeID.
I already have my <employeeID> field. There is no need forthe UserID for me I think. I just need to select the employeeID and append the value to the junction table. Thats what i Think.
I just couldnt revise the code myself.
any help wuld be appreciated.
thank you for all the replies.
Apr 28 2005, 10:13 AM
The attached demo uses EmployeeID throughout the database...
May 9 2005, 11:37 PM
Hi Jack do you think I could have a copy of the survey for Access 97 .I am doing a similar survey at the moment .
May 10 2005, 10:08 AM
Hopefully there is a questionnaire and a survey in the attached...
May 10 2005, 05:22 PM
Hello Jack.I tried to open it this morining but it states unrecognised format.I am doing something wrong.
May 10 2005, 05:40 PM
DRAT! Try the attached... If this does not work send me your email address and I will send the files to you directly....
May 10 2005, 06:03 PM
Terrific works well.Once again thankyou
May 10 2005, 08:36 PM
Phew! I am glad that I finally got it right! Good luck with the demos and continued success with your project....
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here