what kind of selection do you mean?
It sounds like a fairly unusual idea, so I wouldn't expect you to find your answer outside of bespoke programming :-(
Best regards
Shady
how about this for a possibilty
1. db or file holds all possible choices
2. on load the form reads and displays all available choices
3. user selects choice and submits
4. processing script emails the selection to you and removes the option/selection from the db or file
make sense? wouldn't be overly difficult to code in either perl or php. I would figure shady is right that there may not be a predesigned script for this but it is fairly straight forward.
Are you familiar with either perl or php?
Which does your host offer?
[edited by: jatar_k at 2:31 am (utc) on Nov. 6, 2003]
Be careful... You have the makings of a classic 'glare' condition here.
If it is required that two people may never make the same choice, you will have to add steps to confirm to each submitter that his/her selection was accepted, and if not, to offer a new form with the revised currently-available selections.
This kind of system can break down badly under heavy load, even if implemented properly. There's always some unlucky person who submits 10 milliseconds after his/her first choice is taken, then resubmits 10 milliseconds after the second choice is taken... I think you see what I mean here -- the system can be very 'unfair' if several people are selecting simultaneously...
Depending on time scales and traffic, you might even want to implement an automatic page refresh every 3 to 15 seconds to help prevent this problem... Plus, it lets people see the choices dwindling (if that is a benefit to your site).
Too many years spent doing worst-case analysis I guess, but forewarned is forearmed...
Jim
