this same issue exists on a single webserver. there are several options.
1) write you code so it doesn't matter (update if found, use unit counts
instead of add, etc).
2) store a transaction guid with the page, and check if processed
3) disable button (won't prevent a refresh from resubmitting)
-- bruce (sqlwork.com)
"Aeden Jameson" <Aeden
Ja*****@discussions.microsoft.com> wrote in message
news:81**********************************@microsof t.com...
Supose you have NLB'd web servers with affinity set to none. A user
fills out a form whose content will be written to a database. Also
suppose
the impatient user hits the submit button a second time. My question is,
what do you need to detect the duplication submission?