>All that occurs within one template and it all works fine. The problem
>is if the Administrator hits refresh on their browser. The browser
>refreshes the exact same information to the Administrator BUT it also
>re-inserts the exact same data with a new MemberID.
>
>How do I stop that attempt to re-run the insert query when all that's
>occurring is a browser refresh?
You could split it into two scripts.
First one does the insert, the max(memberid) query.
Then have it kick to the next page, passing that new memberID in the URL.
You can do <cflocation> or just put some _javascript_ code at the end of the
script forcing a document page change.
That way, the second page is what someone would be reloading when hitting
'refresh', and all it would do is re-read the existing data based on the
memberID in the URL.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
