depends exactly what you are doing.
What I do in these cases is to have a helper function in a helper class. THis can create a connection to the database, open an SqlCommand, then perform an ExecuteScalar before cleaning up and returning the new Id (returns 0 if an error)
Now that I have the ID, further updating is possible
I also use a single Stored Procedure for Insert/update and check for either 0 or null value for the Id being passed - either method is OK - just set the parameter to have a default value and don't set the SqlCommand parameter when creating the parameter list.
If parameter is present, then it must be an update, otherwise it is an insert
If it was easy, everybody would be doing it.