I think I might be confused. If all people will not have an account wouldn't it be better not to make all people have the account class as a member? I am not too sure what downcasting is, I have not heard of that before, but I will look into it. Another question, if you, lets say, are making a game. You have a default object super class that contains all the information each object for sure will need, then you have a bunch of other classes that inherit from it. Then you want to make an array of some sort to hold all object to do your colision detection and add/delete new objects as necessary. That is considered something wrong with architecture? I have seen a few people use that before, and was somewhat what I was hoping to accomplish. If that is not the best method to go about doing it, I would be happy to figure out new methods. OOP still confuses me a bit. Thank you for your time, and replies.