Ah, sorry for misunderstanding.  I placed the Account Login module on a page to test it out, and it did not render anything once I was logged in, so I'm not sure what you're seeing.  Maybe the module does some sort of check that you're passing and I'm not.  Regardless, I'm now seeing your situation a little better.

My experience with the login module, like I mentioned above, is that it redirects you away from it or just doesn't render if you're already logged in.  Since yours isn't doing that, I'm kind of shooting in the dark here until I can figure out why.  However, one thing that I would suggest that you try is (if possible) to change the URL that you are giving out to send people to the control directly, instead of to a page with the control on it.  For example, instead of http://dotnetnuke.com/tabid/58/default.aspx, send them to http://dotnetnuke.com/ctl/login/default.aspx (or ?ctl=login if you aren't using friendly urls).  That way, the module should only be accessible the first time you hit it, and then will disappear after you're authenticated.  Can you try that out and see if that works any better?

It may sound odd, but I don't actually know the correct URL to send the user to for that default control you mentioned.

However... it works for my needs to show the module only to unauthenticated users.

If I login as host, obviously I still see it.  But when any other user logs in, the module disappears, and I have provided no other way to navigate to their user settings.  so for now, problem solved.

Not sure what I'm going to do about it when I set up the storefront portion... probably  will get into roles at that point.  :-)

Thanks so much for your attention to this matter, I greatly appreciate your assistance and the knowledge share.

Best regards,

Vollerworld