You would probably be ok. I'd be a bit reluctant to do this, myself, though.
The problems might be if MS ever makes a change to the schema or stored
procs that would blow up any of your mods. Also, you need to remember to
make the changes in the membership schema anytime you switch the datastore
that holds your userids (say when you migrate from dev to QA, and then to
prodution, or if you ever had to rebuild your production ASPNETDB).
You might check to see about using personalization properites via the web
config. I think you can use this to create custom name/value pairs that are
stored in ASPNETDB.aspnet_Profile. See this
http://www.ondotnet.com/pub/a/dotnet...on.html?page=1
Jason Vermillion
"perplexed" wrote:
>
>
> On Jan 27, 6:22 pm, "Juan T. Llibre" <nomailrepl...@nowhere.com>
> wrote:
> > Add a column to the database and display that.
>
> Juan, that's right but I guess I was wondering more about
> consequences. It's probably a shot in the dark. It's only testing
> right now so no big deal if something breaks.
>
>