Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a Users table and a profile table. The reason they are separate is because information about the user can be put in before they are registered for the site. The problem I’m running into is that when I set the relationship in Sql Server it wants to create a one to many relationship. I don’t see any way to change this.
I assume you’re creating it using the ASP.NET Membership? If so, simply add a uniqueidentifier column inside your profiles table, set as primary key and you’re good to go. SQL won’t allow you to add more than 1 record for that ID.
This article provides exactly what you need
http://www.asp.net/security/tutorials/storing-additional-user-information-cs