Thanks James. My way around this was to modify the access info for the
survey and allow the respondent group that I created a max responses of 800
-- which I figured would give me some slack for the 600 people who would be
responding. It is working pretty well. Our problem was that the target
group for this survey has a not insignificant amount of churn, and we do
not have a support staff for technical issues, so we figured that it would
be better to deal with a single login for everyone. Any identifying
information that we would need could then be solicited in the survey itself.
It is good to know about the forward/backward behavior though. The main
problem reported has been that they hit their browser back button to review
answers and everything disappears. I will just have to remember to tell
them not to hit back in the instructions next time.
Cheers,
--chris
At 04:45 PM 4/27/2004, James E. Flemer wrote:
>I'm not exactly sure if I follow, but if you intend for all 600 people to
>login as "person", I don't think phpESP will do what you expect. You will
>end up with 1 result (the last one entered). What are you trying to
>achieve? I think the best solution (guessing your needs) would be to make
>a public survey, but restrict access via Apache (htaccess).
>
>As far as back/forward, each user has one response in an authenticated
>survey, and back/forward will load results from that one response. So
>yes, using back/forward with the scenario you describe will allow one
>person to see another's responses (and overwrite them).
>
>In short, do not give multiple people the same username/password!
>-James
>
>Christopher Kolar wrote:
>>Hello everyone. I was wondering if someone could let me know a bit more
>>about how the back/forward feature works in relation to user accounts and
>>groups. Specifically, I have a survey that is private and a groups of
>>people who I want to have fill it out. I set up a respondent account
>>named "person" and added it to group "group" (those are made up of
>>course). I went to the access page and said that the survey is private
>>and that I will accept 600 responses from group "group."
>>I was wondering if the enabling of the back button would be a problem
>>given that the login is being shared by a large number of respondents.
>>If the back functionality stored locally, so that multiple people would
>>all see their own data, or is it stored centrally in the db with the
>>associated login, so someone hitting back might see another person's
>>responses? Unfortunately with the population we work with we cannot set
>>up individual login accounts, but I am hopeful that we will be able to
>>activate the back button for this group in the future.
>>Thanks in advance,
>>--chris
|
