There might be a way to zap a browsers history ... so that the user can't use
back?
However, from a database design standpoint ... if duplicate records are not
allowed then this constraint should be enforced at the database level.
Bill Reichard
Willow Gold
[EMAIL PROTECTED]
http://www.willowgold.com
In a message dated 1/17/01 3:05:47 PM Eastern Standard Time,
[EMAIL PROTECTED] writes:
> No we already have something in the place that checks for a duplicate.
> The problem was it was caching the results of both the search for the
> random number and then inserting it. I tried the CFLocation technique
> as described in an earlier post but it still seems to be entering in
> duplicate values. I have a few other ideas Im gonna try and hopefully
> get this fixed.
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
