you're inserting "$hobbie" (misspelled) and not $hobbies as set above.. also, all of your option values are the same, so no matter what you select it's going to show insert the value as "hobbie" and $database isn't defined, but since you're suppressing the error, you're going to be wondering why it's not working even after addressing the aforementioned. it's also vulnerable to attack btw.
The spelling was intentional. And I solved the problem. As far as "it's also vulnerable to attack btw." would you like to elaborate or offer a solution. I thought this forum was for suppport and solutions.
jack, sorry for the brevity and the run-on sentence.. i was on my way out. what I was alluding to was that one could write a script that could populate your database with "x" number of records. you could handle the validation in any number of ways: an authentic id (unique for every submission), set a session to prevent repeat posting (ie: 1 post every 5 minutes) and/or validate that the post matches the available options (ie: data integrity).
As I mentioned in an earlier post, the script was merely a test to ascertain why the data would not go into the database. This is not the form that I am using in the actual database. And I do have an id set for each client, just not in this script, but thanks for the heads up and i will look into data integrity part.
DS. Didn't know I shouln't be posting here. I use this site for my site development which is CSS and there are a lot of talented people here and since it is "server side coding" I didn't see the problem. I have posted elsewhere on more specific sites, such as the one you mention and no one can ever help. And as it turns out I have solved the problem.