Going back to this question from last week, I didn't see anyone mention the
feature built into CF 7 and above to prevent duplicate form submissions.
It's a simple solution (which of course means it has both pros and cons):
using http://carehart.org/blog/client/index.cfm/2008/3/24/prevent_multiple_
der.
Screen 4
Thank you ... bla bla ... complete ...
Now if you check the db and no possible duplicates then skip screen 2.
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Howard
Sent: 03/20/2008 11:45 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Disc
ECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *Jeff
> Howard
> *Sent:* 03/20/2008 11:45 AM
> *To:* discussion@acfug.org
> *Subject:* Re: [ACFUG Discuss] looking for opinions on duplicate form
> submissions
>
> This is an internal application and js is enabled on all machines and
What Dean said.
Shane
CTek Media
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dean H. Saxe
Sent: Thursday, March 20, 2008 10:03 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] looking for opinions on duplicate form
submissions
Put a
rent Kitchens
Emory University
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Howard
Sent: Thursday, March 20, 2008 11:45 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] looking for opinions on duplicate form submissions
This is an internal application and
IL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Howard
Sent: 03/20/2008 11:45 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] looking for opinions on duplicate form
submissions
This is an internal application and js is enabled on all machines and
everyone MUST use IE here.
e
entered on the form and give them the ability to view those other
entries before saving the form).
Just an idea.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff
Howard
Sent: Thursday, March 20, 2008 11:20 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] lookin
Ajax does not solve your problem. Ajax is a series of methods for UI
control, not business logic. Regardless of your use of Ajax or not
you have a business problem to solve first, implementation and UI
control comes later.
-dhs
Dean H. Saxe, CISSP, CEH
[EMAIL PROTECTED]
"Free speech exe
This is an internal application and js is enabled on all machines and
everyone MUST use IE here.
The issue here is that the user must be the one to decide if it is a
duplicate. I'm merely notifying the user that there is a submission already
that looks identical to what they submitted. Then it's
ean H. Saxe
Sent: Thursday, March 20, 2008 11:16 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] looking for opinions on duplicate form
submissions
I'm one of those users. NoScript is a very good extension if you want
to know what marketing companies and other unsavory types are harve
lf Of Jeff Howard
Sent: Thursday, March 20, 2008 11:20 AM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] looking for opinions on duplicate form
submissions
These duplicates are not necessarily session duplicates. A user, or
even a different user might input the same information from a hard
My first quick fix idea was to run the check, if recordcount GT 0 then throw
the form into wddx and put it in a temp table in the db. if user click
'save' pull the info back out and save and delete the wddx record from the
temp table. if the user clicks 'cancel', just delete the temp file. this
You could still go this route and make the form so that the button is
disabled by default and only gets enabled if JS is on... that circumvents
the "is JS on problem". I've worked on forms in the past and used this
approach. You have the potential of cutting out the people that have JS
turned off
These duplicates are not necessarily session duplicates. A user, or even a
different user might input the same information from a hard-copy form into
the system a day or two later. Basically, I'm trying to look into the
database and compare all fields values with those of the submitted form, and
You ABSOLUTELY MUST validate after submission on the server. And if
you want to stop duplicate submissions, this must be done server
side. ANY client side validation is trivial to bypass.
-dhs
Dean H. Saxe, CISSP, CEH
[EMAIL PROTECTED]
"Dissent is the purest form of patriotism."
--Tho
A couple of things spring to my mind that don't involve ajax.
1. Accept the form and then prompt for the upload. It adds a separate
page but it reduces your duplication.
2. Accept the uploaded document. Yep, save it to your server and if the
data turns out to be a duplicate entry, action="DELETE"
I'm one of those users. NoScript is a very good extension if you want
to know what marketing companies and other unsavory types are
harvesting your surfing habits to target advertising. I enable
scripting on a whitelist of trusted sites only.
-dhs
Dean H. Saxe, CISSP, CEH
[EMAIL PROTECT
I think validating before submitting makes sense (less bandwidth if users
are submitting large files for example). I use mxAjax [
http://www.indiankey.com/mxajax/] for simple validations/lookups in
applications I've written. It is fairly simple to set up and use. You create
a CFC, add it to the set
My first thought is...disable the submit button after its mashed once. My
second thought is, some people disable JavaScript. Now, what type of user
disables JavaScript? Would that type of user go 'mash the button crazy',
does it really matter then? If so, could use Flash(read Flex). Aside fro
Put a unique identifier in the form request, store it in the user's
session before form submission. Once the form is submitted check to
see if the value matches. If so delete it from the session and
continue processing. If the token doesn't match or is nonexistent in
the session, then it
20 matches
Mail list logo