[RESOLVED] [2005] Help with <asp:buttoncolumn>

Ok, here is my code.

asp Code:

<asp:DataGrid runat="server" ID = "testgrid" OnSelectedIndexChanged="testgrid_SelectedIndexChanged" OnItemCommand="Button_Click" Height="40px">
    <HeaderStyle BackColor="Blue" ForeColor = "White"/>
    <Columns >
    <asp:ButtonColumn Text = "View Information" ButtonType="PushButton" ></asp:ButtonColumn>
    </Columns>
    
    </asp:DataGrid>

And in the codebehind I have:

asp.net Code:

void Button_Click(System.Object Sender, System.Web.UI.WebControls.DataGridCommandEventArgs e) 
    {
        MessageBox("Button Pushed!");
    }

Now, when I compile, I'm getting this error:

Error 3 'newpage.Button_Click(object, System.Web.UI.WebControls.DataGridCommandEventArgs)' is inaccessible due to its protection level C:\Documents and Settings\justin\My Documents\Visual Studio 2005\WebSites\AceSite\newpage.aspx 62


I'm kinda stuck...

Thanks for the help,

Justin Fox

public void Button_Click.........

Ok, I changed the method to public, and when I click the button, I get this error.

vb Code:

Invalid postback or callback argument.  Event validation is enabled using <pages
 
 enableEventValidation="true"/> in configuration or <%@ Page EnableEventValidation="true" %> in a page.
 
  For security purposes, this feature verifies that arguments to postback or callback events originate from
 the server control that originally rendered them.  If the data is valid and expected, use the
 ClientScriptManager.RegisterForEventValidation method in order to register the postback or callback data
 
for validation.

I gave it a method to call, I don't get it.
I put that eventenables stuff in my web.config file too.

Thanks,

Justin Fox

I figured out what it was, I wasn't putting:

asp Code:

if(!IsPostBack)
{
 
}

Around my binding of my datagrid in my page_load function.
so it was trying to bind the data everytime I pushed the button, and
I guess it was doing away with my OnItemCommand stuff.

Justin

Yes, good work.

The Page.IsPostBack is where people often get stuck the first time. When you rebind the control on every load, the viewstate information for it is lost. The viewstate information is what the application usually needs to know that an event has been raised or that some value has changed somewhere. By doing the postback check, the viewstate is preserved.