Hello Ryan,
I think it is the right article when we wants to add some customized user
properties like Address, phone.... To implement it, we need to create our
own MembershipUser and Membership provider.
For a customized Membership provider, it may access its own data store, not
the original database(aspnetdb) provided by AspNetSqlMembershipProvider.
Like the Access database in the article
(
http://msdn2.microsoft.com/en-us/lib...30(d=ide).aspx.) Therefore,
it is not "split into 2 tables", it is a complete new table in new data
store.
For more questions on asp.net security, you may post in
microsoft.public.dotnet.framework.aspnet.security. I will work with you
there.
Thanks,
Luke Zhang
Microsoft Online Community Lead
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
(This posting is provided "AS IS", with no warranties, and confers no
rights.)