Greg, I'm rereading your solution again, but I'm not sure which primary key that you mean. For the actual answer/result into the results table? So insert, get the PK,then write that to a cookie? You say that I have a primary key on the form page, and I do, but it's the poll Id. That poll can be answered multiple times on one machine, since alot of our user base uses community machines. I just want it set up so that they MUST click a poll answer and submit each time they vote.
>one solution is to use a 3-page approach.
>
>form page -> update page -> thank you page
>
>the form page is self-explanatory. contains your form.
>the update page has your updat query in it. once the query succeeds,
>do a <cflocation> to...
>
>the thank you page. this is the page that lets your user know the
>update completed successfully. and since it contains no UPDATE query
>itself, it can be refreshed over and over and over with no adverse
>effects on your data :)
>
>
>
>
>On Wed, 22 Sep 2004 14:04:36 -0400, Daniel Kessler <[EMAIL PROTECTED]> wrote:
>>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
