Data binding: object reference required

[cppquester]

I have a data set
MMSDataAccess
with:
public partial class MMSDataSet : System.Data.Dat aSet {

...

private TB_ACTHEATDATAD ataTable tableTB_ACTHEAT DATA;

...

public TB_ACTHEATDATAD ataTable TB_ACTHEATDATA {
get {
return this.tableTB_AC THEATDATA;
}
}

...
}
and a component for editin it
MMSDBEditContro l:

with

partial class MMSDBEditContro l
{

private void InitializeCompo nent()
{
...
this.mMSDataSet = new MMSDataAccess.M MSDataSet();
...
}

}
Above is all designer gernerated code.

But when I do:

using MMSDataAccess;
using MMSDataAccess.M MSDataSetTableA dapters;

namespace MMSDBEdit
{

public partial class MMSDBEditContro l : UserControl
{
public MMSDBEditContro l()
{
InitializeCompo nent();
TB_ACTHEATDATAT ableAdapter.Fil l( this.mMSDataSet .TB_ACTHEATDATA ); //
Error here
}

....
}
}
I get
Error 1 An object reference is required for the nonstatic field,
method, or property
'MMSDataAccess. MMSDataSetTable Adapters.TB_ACT HEATDATATableAd apter.Fill(MMSD ataAccess.MMSDa taSet.TB_ACTHEA TDATADataTable) '
C:\Project\MMS\ MMSDBEditContro l.cs 20
Does somebody understand why that is?
I would think the Fill method got exactly what it is demanding.

Thanks,
Marc

[cppquester]

On Nov 26, 10:41 am, cppques...@goog lemail.com wrote:

I have a data set
MMSDataAccess
with:
public partial class MMSDataSet : System.Data.Dat aSet {

...

private TB_ACTHEATDATAD ataTable tableTB_ACTHEAT DATA;

...

public TB_ACTHEATDATAD ataTable TB_ACTHEATDATA {
get {
return this.tableTB_AC THEATDATA;
}
}

...
}

and a component for editin it
MMSDBEditContro l:

with

partial class MMSDBEditContro l
{

private void InitializeCompo nent()
{
...
this.mMSDataSet = new MMSDataAccess.M MSDataSet();
...
}

}

Above is all designer gernerated code.

But when I do:

using MMSDataAccess;
using MMSDataAccess.M MSDataSetTableA dapters;

namespace MMSDBEdit
{

public partial class MMSDBEditContro l : UserControl
{
public MMSDBEditContro l()
{
InitializeCompo nent();

TB_ACTHEATDATAT ableAdapter.Fil l( this.mMSDataSet .TB_ACTHEATDATA ); //
Error here
}

...
}

}

I get
Error 1 An object reference is required for the nonstatic field,
method, or property
'MMSDataAccess. MMSDataSetTable Adapters.TB_ACT HEATDATATableAd apter.Fill(MMSD ataAccess.MMSDa taSet.TB_ACTHEA TDATADataTable) '
C:\Project\MMS\ MMSDBEditContro l.cs 20

Does somebody understand why that is?
I would think the Fill method got exactly what it is demanding.

Thanks,
Marc

ok, found the solution myself:
The object reference required related to the object on which Fill was
called
(this).

However: Why there is no tebale adapter hold by the MMSDataSet
as it holds the table itself as well?

[Jon Skeet [C# MVP]]

On Nov 26, 10:11 am, cppques...@goog lemail.com wrote:

<snip>

The object reference required related to the object on which Fill was
called (this).

However: Why there is no tebale adapter hold by the MMSDataSet
as it holds the table itself as well?

The adapter populates the data set, but there's no reason for the data
set to keep hold of the table adapter. In particular, a single table
adapter could populate many data sets. It's just a conduit between the
in memory data and the database, really.

Jon

[cppquester]

On Nov 26, 11:19 am, "Jon Skeet [C# MVP]" <[e-mail] mwrote:

On Nov 26, 10:11 am, cppques...@goog lemail.com wrote:

<snip>

The object reference required related to the object on which Fill was
called (this).

However: Why there is no tebale adapter hold by the MMSDataSet
as it holds the table itself as well?

The adapter populates the data set, but there's no reason for the data
set to keep hold of the table adapter. In particular, a single table
adapter could populate many data sets. It's just a conduit between the
in memory data and the database, really.

Jon

Thanks for the answer.
So everytime a TA is needed I should create it new?
That leaves no big overhead? Or is there even a benefit
(e.g. releasing memory used for the fill)?

Marc

[Jon Skeet [C# MVP]]

On Nov 26, 4:22 pm, cppques...@goog lemail.com wrote:

Thanks for the answer.
So everytime a TA is needed I should create it new?
That leaves no big overhead? Or is there even a benefit
(e.g. releasing memory used for the fill)?

I'm not an expert on the adapter side of things, but I believe it's
fine to create a new one each time.

Jon