Constructor firing Inheritance in C#

[RickHodder]

I'm having a problem, and here is a simplified example of code that
demonstrates it:
public class BizObj
{
public string TableName="";
private DataSet oData;

public BizObj()
{
LoadData();
}

public void LoadData()
{
SqlConnection oConn = new SqlConnection(" ...");
SqlDataAdapter oAdapter = new SqlDataAdapter( "SELECT * FROM
"+this.TableNam e,oConn);
oAdapter.Fill(o Data);

}
}

public class AuthorBizObj: BizObj
{
public AuthorBizObj()
{
this.TableName= "Authors";
}
}

Now, because the base class constructor fires first, LoadData is called
before the TableName can be set to "Authors".

So I try to override the TableName field in the following manner, hoping
that it will be set before the constructor methods fire:
public class AuthorBizObj: BizObj
{
public string TableName="Auth ors";

public AuthorBizObj()
{
}
}

But I get a compile warning: "The keyword new is required on
AuthorBizObj.Ta bleName because it hides inherited member BizObj.TableNam e."

I'm not trying to hide the member, I'm trying to override it.

How can I make sure that the TableName field has the value "Authors" before
the BizObj constructor fires?

<b>This question is strictly about inheritance.</b>

You might say "Pass a value for TableName to the constructor" , but I think
that the Authors bizobj should know its table, not have its name passed into
it.

You might ask "Why do you want to call LoadData in the constructor?" or say
"Call LoadData after you have instantiated AuthorBizObj, not in the
constructor" - I'm actually not creating bizobjs, this is just some sample
code that demonstrates the problem, I'm trying to override a member field,
not figure out where LoadData should be called.

Thanks,
--
Rick Hodder

[Jon Skeet [C# MVP]]

RickHodder wrote:

<snip>

I guess the best way to re-state my request is "I have code in a constructor
that calls out to another method . When creating subclasses of this class,
how can I override the values of fields (using initializers maybe??) so that
when the base class calls out to the method, the field is initialized to the
value appropriate for the subclass"

You *could* have an Init method which could be overridden in derived
classes. However, my best advice would be to try to avoid that design
pattern in the first place.

Jon

[Darren]

It is best to keep as much of the initialization code in the base as possible.
That way, if your base class needs to change there is less impact on derived classes.
Jon Skeet [C# MVP] wrote:

RickHodder wrote:

<snip>

I guess the best way to re-state my request is "I have code in a constructor
that calls out to another method . When creating subclasses of this class,
how can I override the values of fields (using initializers maybe??) so that
when the base class calls out to the method, the field is initialized to the
value appropriate for the subclass"

You *could* have an Init method which could be overridden in derived
classes. However, my best advice would be to try to avoid that design
pattern in the first place.

Jon