I did a bunch of searches for adding fields to the signup form but I couldn't find anything.
I'd like to create a database containing user information for people who have userid's in my databases. All of my databases use the same .pass file. Basically what I'd want to do is add a bunch of fields to the signup form - stuff like location, date signed up, rider style etc. (I have a biking website)
I'd set up a relation between the userid of the main databases and the user database. Main database has a "posted by" field that clicks into the user database.
Only 1 problem though, currently creating a new account uses this submit code:
<input type="SUBMIT" name="signup" value="Create">
And adding to the database is this:
<INPUT TYPE="SUBMIT" NAME="add_record" VALUE="Add Record">
How would I combine the two together so when the person signs up, they are added to both the .pass file and the user database?
Basically, I'd allow users to search through the user database for people in their area to go biking with. Of course there'd be an option for not making the user info visible to the public.
Is this too ambitious?
-----------
Jason Dulberg
Extreme MTB
http://extreme.nas.net
I'd like to create a database containing user information for people who have userid's in my databases. All of my databases use the same .pass file. Basically what I'd want to do is add a bunch of fields to the signup form - stuff like location, date signed up, rider style etc. (I have a biking website)
I'd set up a relation between the userid of the main databases and the user database. Main database has a "posted by" field that clicks into the user database.
Only 1 problem though, currently creating a new account uses this submit code:
<input type="SUBMIT" name="signup" value="Create">
And adding to the database is this:
<INPUT TYPE="SUBMIT" NAME="add_record" VALUE="Add Record">
How would I combine the two together so when the person signs up, they are added to both the .pass file and the user database?
Basically, I'd allow users to search through the user database for people in their area to go biking with. Of course there'd be an option for not making the user info visible to the public.
Is this too ambitious?
-----------
Jason Dulberg
Extreme MTB
http://extreme.nas.net