Actually what we do is to do the insert and then redirect to a search
action that pulls up the new record. This allows us better
verification that things were added correctly, rather than depending
on the use of <@arg > s, etc. And we give the user an opportunity to
edit their info if what is shown is in error.
it's a bit more work for the database, but makes for a more accurate
user experience.
>That sounds like a better solution and easier to implement. All I have to do
>is take the results out of the taf and into another which is the redirect.
>
>Can I do a redirect that just takes them to another action in the taf with
>the results. Seems that would work also.
>
>Dan
>
>on 6/7/02 11:38 AM, Dale Graham at [EMAIL PROTECTED] wrote:
>
>>> Is the something I can put into the Meta data section of a specific HTML
>>> page that will prevent the user from refreshing the page.
>>
>>
>>>
>>> I have a result page after a course registration that if refreshed will of
>>> course register them a second time for the same course. It messes up the
>>> course count.
>>
>> What we do is to register people and then do a redirect to a page
>> with the results. Then they can press the reload button until the
>> cows come home, and they won't add themselves again.
>
>--
>Dan Stein
>Digital Software Solutions
>799 Evergreen Circle
>Telford PA 18969
>Land: 215-799-0192
>Mobile: 610-256-2843
>FMP, WiTango, EDI,SQL 2000
>[EMAIL PROTECTED]
>www.dss-db.com
>
>
>________________________________________________________________________
>TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
