I want to set up a Membership provider for an asp.net 2.0 application. The provider will use a sql server 2005 database. The user table contains email addess and user name and password and security question and security answer but also various other fields for address and postcode and job title and various telephone numbers etc. I also want to hold adresses in a separte table linked by a foreign key and also security questiion details, user types and user status details in separate tables and have access to the data managed through the membership provider. What I'm confused about is whether I can include these extra fields in the user table and use the built in membership provider or whether I need to extend the built in membership provider or whether I need to produce a custom membership provider.