> I add a field in into Aspnet_Users tables.
You're not supposed to do that. You should think of the MembershipProviders
as "black boxes", meaning the internal implementation details are not to
knwo known. Also, you're violating the intent of the member ship provider.
It's supposed to be there just as a repository of authentication information.
Add more information unrelated to authentication is breaking the encapsulation.
Plus on top of it all, the provider has no clue that you've added that information
to its store.
What you want to use is the Profile. It allows arbitrary information associated
with a user to be stored in the database. The ProfileProvider has a seperate
role from the MembershipProvider and it's important to keep them distinct.
This was recently discussed on the forums at
www.asp.net: http://forums.asp.net/864182/ShowPost.aspx How can I add this field to CreateUserWizard?
The CreateUserWizard allows you to add steps, so you can collect any additional
profile data there then handle the CreatingUser event and then save your
additional profile data then.
-Brock
DevelopMentor
http://staff.develop.com/ballen 
