Object Reference not set

ZeroFactorial · April 3rd, 2009, 05:03 PM

Hi all again.

Another productive week of coding, debugging and learning!

I have gotten my AETransfers.aspx up working great and it brings you to AETransfer.aspx when you select Add New Transfer.

The form comes up the logic to display certain parts of the form load as should.
I fill the form out, and press save and I get the following error in my LoadObject from Screen block: Object Reference not set to an instance of an object.

It points to the baseEO.pName = pName.Text;
To get to where I am at I followed the pattern used in the Administration/Users.aspx and Administration/User.aspx pages. The pName.Text is not null and I have verified that the data is being passed. Any idea as to what it could be looking for or what I need to do to correct it?

Code:

protectedoverridevoid LoadObjectFromScreen(AETransfersEO baseEO)
{
    baseEO.pName = pName.Text;
    baseEO.RequestDate = Convert.ToDateTime(reqDate.Text);
    baseEO.dob = Convert.ToDateTime(dob.Text);
    baseEO.transFacility = transFacility.SelectedValue.ToString();
    baseEO.facilityPhone = facilityPhone.Text;
    baseEO.personCalling = personCalling.Text; 
}

Here is my Save Method

Code:


void Master_SaveButton_Click(object sender, EventArgs e)
{
ENTValidationErrors validationErrors = newENTValidationErrors();
AETransfersEO aETransfer = (AETransfersEO)ViewState[VIEW_STATE_KEY_AETRANSFER];
LoadObjectFromScreen(aETransfer);
 
if (!aETransfer.Save(ref validationErrors, 1))
{
Master.ValidationErrors = validationErrors;
}
else
{
GoToGridPage();
}

Thanks

Corsair · April 4th, 2009, 12:51 AM

Is it possible that the offending null object is actually aETransfer? Did you put it in the ViewState in LoadScreenFromObject?

If you haven't already, put a breakpoint on the line AETransfersEO aETransfer = (AETransfersEO)ViewState[VIEW_STATE_KEY_AETRANSFER]; and step through the code from there.

The code looks right as posted, so it's probably something relatively simple (like a typo in an ID).

At least, that's my two cents (not ajdusted for inflation)...

Tim

varallov · April 4th, 2009, 09:48 AM

Usually when this occurs it is because the EO object wasn't saved to the ViewState in the LoadScreenFromObject method as Tim said.

ZeroFactorial · April 7th, 2009, 07:38 PM

Thanks for the replies everyone.

Tim what you pointed out was the problem.
Guess too many long hours will get you over looking the simple things.

I actually had it in the LoadScreenfromObject but it was commented out since I was testing something else. Thanks for bringing that to my attention. I suffer from making simple things complicated syndrome.

Corsair · April 9th, 2009, 02:06 AM

Glad to be able to help. I understand the whole not seeing the forest for the trees problem.

And I'm willing to bet that I can make simple things more complicated than you can :)

Tim