Earlier today I was reading through some other examples and I figured it out. I found a much simpler way than the other example I was trying to learn from. It was something more like the way Stepterr was recommending. I actually ended up making a few changes to all three of the pages I was referencing initially. Atli, thank you for the assistance in the syntax of things.

Thanks to everyone for all of the assistance with my new adventure...

No, I'm not doing anything with arrays in my form... but the info from each input from the form is put into an array in $_POST; if i understand Atli correctly. That $_POST array of data was then to be sent through the foreach() loop which would parse the info into the appropriate places in the UPDATE query. At least that's how I thought it should work -- but doesn't. I've tried the method you have suggested and it unfortunately does not work either....

Atli,

Thank you for your response. You've pushed me along in my PHP learning experience. On my second page I was able to substitute $_POST for $HTTP_POST_VARS perfectly fine -- the query still successfully pulls the record's fields and inserts them into the html form for editing. However, on the third page (the PHP page updating the mysql table) is still unsuccessful.

I understand that the foreach() loop is looking...

Brett,

I read that bit about the change from $HTTP_POST_VARS to using $_POST. I have register_global s set to on and am using PHP 4.3. I understand that w/ register_global s on then $HTTP_POST_VARS should behave the same as it is would treated as a global variable. I can't seem to get it to work out yet.

I did just see something about setting the "name=" portions of my form inputs to (all the same) "name...

Setup: I only have one database with one table in it. The first page has a form that adds a record (w/ 6 fields in it) to the mySQL database's lone table via PHP. This works fine. I also have a PHP table that displays all records in my database on this same page. This too works fine. I have my table set up so that there is a 7th field, called "rid" to act as a "record id" or unique identifying field. This is primary and auto-incremented....