in reply to Re: Sending Data
in thread Sending Data

Actually, I thought I had a good grasp of CGI, I admit, I'm not as good as some people with putting a webpage in my perl script, reading ovid the other day did help me a bit. Also,I have programmed in a lot of languages, and Perl is one I always seem to have trouble with. I guess 3 years of doing this was wasted? Plus. I obviously didn't explain my self.

The example I gave for the form, wrong word, webpage, is made from another form, all the data is already sent to it. I use a webpage form to get the data, and perl script to process, the data, and another script to write it. I would love to eliminate the 2nd script, but for some reason, all of these tutorials I have read give me no help what so ever.

All I want to do is to put a send button on the bottom of the webpage, have the user click it, and to write the data and give a confirmation webpage.

I have everything working good, except for the writing. When I use param, the button click wants to repost the data, and it was only sent there from another form. Does any one know a way I cannot lose any data.

Is there any way to get an ok, send, I decided to rename it button to work, so I can just check for a yes. I know it is not the way I should do, but there is NO help I can find in these tutorials. I realy don't want to post, I just want ot know if the user is ok with the data.

I will be happy to send complete html and perl scripts to anyone who wants it.

Joseph A. Ruffino
Automated Systems Assistant
Gail Borden Public Library District
270 N. Grove Ave
Elgin, Il, 60120
847-742-2411 x5986

Replies are listed 'Best First'.
Re^3: Sending Data
by mscerra (Monk) on Aug 12, 2004 at 20:46 UTC
    "I have everything working good, except for the writing. When I use param, the button click wants to repost the data, and it was only sent there from another form. Does any one know a way I cannot lose any data."

    If you use hidden fields you can keep the data on a repost. Just read from the hidden fields.

    Another option, which probably is be overkill, is CGI::Session. You could keep the information as a session variable and pull it out as needed later on.

    Hope it helps.