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
if they're identical I'm displaying a message saying something to the effect
of "check these and make sure you're not duplicating someone's work".  If
after comparing, they decide that it's not a duplicate they hit ok and it
commits.

The trick here, is that all the form data can be identical and something in
the attachments could be different, so the user has to look at the previous
entries to decide if it's a duplicate or not and then click 'save' or
'cancel'.

On Thu, Mar 20, 2008 at 11:03 AM, Dean H. Saxe <[EMAIL PROTECTED]>
wrote:

> 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 its a duplicate or out of order submission.
> -dhs
>
>
> Dean H. Saxe, CISSP, CEH
> [EMAIL PROTECTED]
> "Free speech exercised both individually and through a free press, is a
> necessity in any country where people are themselves free."
>     -- Theodore Roosevelt, 1918
>
>
>   On Mar 20, 2008, at 10:51 AM, Jeff Howard wrote:
>
>   I'm working on an application where a form is submitted along with
> various attachments (doc, pdf, xls, etc).  Apparently users are submitting
> the same request several times and I've been asked to address this issue.
> At first thought, it seemed quick and simple to me, but as I've started
> working on it I can't decide exactly how to handle the attachments in
> associated with the form in the most efficient way.
>
> That brings me here.  I was looking for suggestions on how to handle the
> attachments while I run validation on the db to see if the input from the
> form already exists in the db.  It seems like something that would be
> perfect for AJAX to handle, but my AJAX skills are virtually nonexistent.
> So, without using AJAX (or if you can break it down using AJAX for a novice)
> how would you handle the situation?
>
> The main issue I'm having, is that if I do the validation after the form
> submission, CF is assigning a temp directory to my attachment file.  So what
> is submitted as this: "C:\Documents and Settings\JHoward\Desktop\PO Request
> mods.doc"  ends up as this after submission and validation:
> "C:\ColdFusion8\runtime\servers\coldfusion\SERVER-INF\temp\wwwroot-tmp\neotmp13963.tmp
>  "
> and then when I pass it to the CFFILE, it tells me the file doesn't exist.
>
> I'm really just looking at the different ways other people would handle
> this situation to try and decide so any input would be great.
>
> Thanks in advance.
>
> Jeff
>
> -------------------------------------------------------------
> Annual Sponsor - Figleaf Software <http://www.figleaf.com/>
>
> To unsubscribe from this list, manage your profile @
> http://www.acfug.org?fa=login.edituserform<http://www.acfug.org/?fa=login.edituserform>
>
> For more info, see http://www.acfug.org/mailinglists
> Archive @ http://www.mail-archive.com/discussion%40acfug.org/
> List hosted by FusionLink <http://www.fusionlink.com/>
> -------------------------------------------------------------
>
>
>



-------------------------------------------------------------
Annual Sponsor FigLeaf Software - http://www.figleaf.com

To unsubscribe from this list, manage your profile @ 
http://www.acfug.org?fa=login.edituserform

For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------

Reply via email to