Hello Everyone and thanks for your help in advance. I am delving into the use of the membership API for a number of sites that I develop and host. However, I am stuck on a few concepts that may be completely obvious, but not to me. First, I need the ability to collect customized data when a user creates a profile and then be able to access it for other uses within the application. The SQL Server setup wizard appears to set up a generic database table that I question whether it has the flexibility for my needs. Additionally, am I correct in thinking that one membership table is set up in the SQL Server for all applications to use, or do you set up a new table for each database?
I'm not sure if I am making sense with my questions, but hope somemone can give me some insight on real world implementation.
Thanks.
...
Go to the complete details ...