I think I understand your problem... Here are two MSDN articles you should read carefully:
1. Implementing a Membership Provider - Lists guidelines to keep in mind when implementing your own Provider. Also lists the members that you need to override from the base class (and its base class - ProviderBase). <http://msdn.microsoft.com/en-us/library/f1kyba5e(loband).aspx> 2. Sample Implementation - A full code sample. Enjoy ! <http://msdn.microsoft.com/en-us/library/44w5aswa(loband).aspx> <http://msdn.microsoft.com/en-us/library/6tc47t75.aspx> On May 12, 8:25 pm, Michael_Burgess <[email protected]> wrote: > Hi there, > > Thanks for the reply. > > I probably knew it wouldn't make much sense! > > I'm new to membership stuff yeah. Just don't like the way that > additional profile info is stored in like 2 or 3 columns by default. I > want to be able to knock up some reports and other things that may > need user profile info, so I want it stored in a manner that is easily > queryable. > > If I could find a good guide on writing a custom profile provider then > I may be able to use this - can anyone suggest one? >
