Re: Help with ASP.NET Memberships
- From: "Jonathan Wood" <jwood@xxxxxxxxxxxxxxxx>
- Date: Mon, 15 Oct 2007 17:00:41 -0600
I just want to make sure I understand.
So you don't see any need for a separate database, but that I should add separate tables for storing my application's user data, even if there is some overlap. Is that correct?
At this point, I should probably take the path of least resistance.
Thanks.
--
Jonathan Wood
SoftCircuits Programming
http://www.softcircuits.com
"Scott M." <s-mar@xxxxxxxxxxxxx> wrote in message news:e0clM33DIHA.5160@xxxxxxxxxxxxxxxxxxxxxxx
Are you recommending I create a new database so that I have two different databases that store my users' data?
No, you could create new tables in the membership database if needed, but I wouldn't mess with any of the auto-generated stuff.
.
- Follow-Ups:
- Re: Help with ASP.NET Memberships
- From: Scott M.
- Re: Help with ASP.NET Memberships
- References:
- Help with ASP.NET Memberships
- From: Jonathan Wood
- Re: Help with ASP.NET Memberships
- From: Scott M.
- Re: Help with ASP.NET Memberships
- From: Jonathan Wood
- Re: Help with ASP.NET Memberships
- From: Scott M.
- Help with ASP.NET Memberships
- Prev by Date: Re: ASP .NET 2.0 Unanswered questions...
- Next by Date: Re: Events and Properties
- Previous by thread: Re: Help with ASP.NET Memberships
- Next by thread: Re: Help with ASP.NET Memberships
- Index(es):
Relevant Pages
|