Membership Control Advice Wanted

[Rusty Hill]

I am creating a web app to be shared amongst companies. Each user's
credentials will be in the common ASP.NET membership database. Each company
will have their own data base.

I need to be able to correlate each user to their company so I know what
connection string (which I want to store in the membership database as well)
to use to get their data. Please note that my users will not be able to
create their own profiles over the web.

I was thinking about modifying the login control to allow a field for the
company name and see if I could store that information with the login
credentials. The other thought I had was using the CreateUserWizard control
for an internal app and capture the company name there and still have it
stored in the membership database.

My question is what is the best way to do this and still have the data
stored in the ASP.NET membership database?

Pointers to any articles or links would be of great assistance. Thank you.

 

[Cowboy \(Gregory A. Beamer\)]

The Membership API stores the application the person is using. This is your
key to what application they are going to use and you do not need to store
this information, again, in profile. You then add another table that has
connection string, place the strings by app name or GUID in config, or
extend the aspnet_applications table.

You can have as many applications in a single database as you desire.