OK,

I've learned basic VB, and, as is always the case when I learn something new, I'm more confused than ever.

So, let me take you through a scenario, perhaps you and others could help/annotate so as to provide a thicko like me with the info to get what I want (which I believe to be something quite simple, which is why I am so uterly frustrated by my inability to nail it down) As before, for the sake of argument, the site in question is based exactly on the dating website model....here goes.

Steps: 

1. Member joins via the the create user wizard - this creates a unique identifier (ApplicationID) in the ASPNETDB.MDF database.

2. Either then or at a another time the member logs into the members area and enters extra info (name, address etc) onto a new table (memdets) within the ASPNETDB.MDF database.

3. Either then or at another time the member logs into the members area and enters further info (vital stats of person member would like to meet) onto a further new table (wantsdets) within the ASPNETDB.MDF database.

4. A user can access a table of information sourced from both 'memdets' and 'wantsdets' that shows where they live and what kind of date they're after.

Here are the questions:

Re steps 2 and 3: How do I program the submit button to submit info gathered via text boxes, tick boxes, radio buttons to the new tables - i.e. how should the VB in the codebehind look?

Re steps 2 and 3: How do I ensure that when a member submits data on the 'memdets' and 'wantsdets' tables (possibly immediately, possibly days later) that that data is automatically 'stamped' with the ApplicationID unique identifier, given that the member won't know their ApplicationID - i.e. that the database knows that the data just collected should be associated with a given user?

That's it for the moment, but I'm sure there'll be more!

1. In your submit button create an insert query depending upon your requirements.  Make a connection to the db and then save it in the db.  If you have a DataAccessLayer or BusinessLayer then send the info to the appropriate objects.  Following is a very basic example: 

   Dim queryString as String = yourquerygoesinhere
   Using connection As New SqlConnection(connectionString)
           Dim command As New SqlCommand(queryString, connection)
           command.Connection.Open()
           command.ExecuteNonQuery()
       End Using
   

2. I don't think you need to store/pass the ApplicationID because the user's in your application are unique. They have a unique UserID and you can use this UserID to be your key in the details table.

If you have any doubts, reply to the post.

Thanks codeasp,

Can anyone tell me where I can find online learning resources that deal specifically with the issue of using VB code behind to tell the submit button to submit data to a database, if you could it would help me greatly.

Thanks

Michael