GET vs POST

Barb54

I have a multipage form I need to create.
Page 1 - check for login and if need be get logged in first
fld1 is text
fld2 is text
fld3 is radio buttons A, B, C, D - only 1 can be selected
if A or B go to page2_A
if C go to page2_C
if D go to page2_D

I want to hold the form data from Page1 so I can combine them with selections on Page 2 before posting all the information to the database.

Page 2_A - show the table associated with radio choice
if A - value in table added to the already existing array
if B - value in table *2 then added to already existing array

Page 3_C and D like "if A" just different tables

Is it possible to do this all in 1 form or do I really need to do it in 2 pages? All 4 tables I'm connecting to have exact same set up except data in flds.

A nudge would help. If I use a 2 page form, do I use Post in page 1 or Get? Or is it the other way around? I am confused, lol. Nothing new.

Thanks in advance,
Barb

AstroTeg

When to use GET: when you wish to pass parameters to a web page AND allow the user to modify them or bookmark them. A good place to do this is search result pages. Use GET to toss the search parameters on the URL and the user can bookmark this for later use if they wish.

When to use POST: when you wish to hide the form data and you wish to keep the URL(s) data free. Although not bullet proof, it does make it a little more difficult for a user to change/fake the form data (key here is just a "little" - at least they can't change it by just putting it up on the URL).

From here, you should be able to answer your question as to which one to use...

Barb54

Thanks for your feedback. I appreciate it. So, it looks like I will go with Post and NOT Get, lol because of username and pw fields.

I also found a couple of threads that might help me from there. I still don't understand combining cookies and sessions as well as the username and pw. I am usin MD5pw and MD5Hash in the program I downloaded. It does not use cookies, but I think I want to inlcude them as well.

Any thoughts on that? My users don't want to have to remember their passwords everytime they load the site. Any options other than the use of cookies?

Thanks,
Barb