So if I follow the guidelines in Chapter 16 and use the Membership Application Service to manage my users, I see that each user gets an unique UserID in the database (accessible by "ProviderUserKey" property of the the Membership User class).

I want to make my own database tables that point to this user. If I make another table in the same database, it seems like using this key is the appropriate way to point to my user. Based on the discussions in Chapter 12, it would make sense to mark such a reference as a foreign key.

But then I got nervous, is it ok to do that? Could making a reference into the membership table mess things up in ways I don't yet understand?

Thanks.

Hi there,

Yes, it's OK to do. The users tables are just tables in your database, so it's OK to refer to them.

Instead of referring to its internal ID, you could also point to the user's User Name as that can be a unique key too.

Cheers,

Imar

__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!