Ian Looney wrote:The member gets instantiated first and not all Members are Players.
Its only later does a member become a Player.
I could declare a Member object in the Player class and link it that way;
...
I was just hoping it could be done??
Just because it can be done syntactically doesn't mean that it's the right thing to do conceptually. What's the idea you're trying to represent in your program by "linking" Member and Player? Do players have essentially the same behaviors and attributes that a member has? When you say "A member becomes a player later on" the first thing that comes to my mind is an "isPlayer" attribute in the Member class. This attribute will be false initially, then some time later when certain conditions are met, the attribute is set to true. It could be as simple as that without having to resort to inheritance or composition.