I recently developed a survey prototype following the general methodology I had used years before at another site. Since this implementation included a Web interface, it proved to be more complicated than I had expected. This involved an "Active State" PERL interface and a Web hosting site as well as Active Links, Filters and macros. Eventually, I plan to add an escalation to bypass the human interface form where the time periods to survey are selected. Since the workflow schematic is all on paper, I can't that (unless I take a picture and download it). I'll be happy to contribute what I can to any interested parties.
One site you may want to check out is the NCSU helpdesk which has a very good example of a clean, concise survey interfaced with a PERL main module: http://help.ncsu.edu/services/survey/survey.pl?callid=###### where ###### is the actual ticket number of your ticket. If you open up a dialogue with them you will find them very accommodating. I checked out a good number of COTS packages for possible use and found that despite promises and assurances from the Reps, every one of them fell short of the basic functionality we required. What we wanted was very simple but we did not want our users logging in to our Remedy system and we did want the capability of a sliding "Likert" scale response in a Web interface. Feel free to contact me directly if you think I can be of help. Don Moore SAIC-HCC Rockville [EMAIL PROTECTED] (301) 998-7340 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
