im using the createuserwizard control for a multi page signup and within the ASPNETDB database ive included my own table for my additional customer data. (aspnet_Customers)
i was about to create a stored procedure for inserting my data into this table and noticed that there are already 2 stored procedures related to creating users within the ASPNETDB database -
aspnet_Users_CreateUser
aspnet_Membership_CreateUser
Am i better off just using one of these to insert the additional form fields into my table (i especially need the unique id thats set up in these procedures for the userid field of my database).
Or would there be a valid reason to have a stored procedure just for my new table (eg aspnet_Customers_CreateUser)
Another thought i had was simply moving my database fields from the table i created into the aspnet_Users table so using that stored procedure that way.
I presuming they would be nothing to stop me doing this? ...
Go to the complete details ...