I am reading user information from the user table and am getting weird results:

                    lblTesting.Text &= "<br>FirstName: " & UserController.GetCurrentUserInfo().FirstName & "<br>"
                    lblTesting.Text &= "<br>CreatedOnDate: " & UserController.GetCurrentUserInfo().CreatedOnDate & "<br>"
                    lblTesting.Text &= "<br>CreatedByUserID: " & UserController.GetCurrentUserInfo().CreatedByUserID & "<br>"

What happens is the first line works great, get's my name.  The next two do not get the right information:

DisplayName: Randy Ansems
CreatedByUserID: -1
CreatedOnDate: 12:00:00 AM

The CreatedByUserID should be 1 (+1) and the date should be last week sometime.

Any thoughts?  What am I missing?

Thanks for the comment, but I am actually reading this from the database for already created users.  To clarify:  I have 10 users who have registered over the past month, when I retrieve their info from the DB to display on a module I know their user ID and/or I can iterate through the list.

The problem being is that the two fields highlighted are not correct b/c I can see the datat in the user table being there as correct:

DisplayName: Randy Ansems
CreatedByUserID: -1
CreatedOnDate: 12:00:00 AM

CreatedByUserID should be a "1" for some b/c they were created by the admin, me.  The date should show a correct date.  I will use CreatedOnDate.ToShortDateString() but the date/time is still null.

Now I get:

DisplayName: Randy Ansems
FirstName: Randy
CreatedOnDate: Monday, January 01, 0001
CreatedByUserID: -1

as output....thoughts?

Now we are getting somewhere.  The created date works, but the Created by user did not.  What I am trying for is if someone of my staff creates a new user (member) they get rewarded, and or they will have some special privileges for the users they created.  

The problem of course right now is that I cannot see from DNN who created the user.  Even though it is stored in the user database correctly.  I might just have to do a DataReader with a stored proc to pull it our, but seems clunky and unnecessary.