MSDN Examples flawed

Ask a Question related to ASP.NET Data Grid Control, Design and Development.

  1. #1

    Default MSDN Examples flawed

    Hi all,

    I think there is an inherent problem with most examples on the internet
    (with MSDN, too!) showing datagrid's databinding. Here is, how they look
    like:

    ========================
    On Page_Load
    if !IsPostBack: BindGrid()

    On_Edit
    Set datagrid's EditItem to clicked item
    BindGrid

    void BindGrid()
    Fill DataSet through dataadapter
    DataGrid.DataBind()
    ========================

    Imagine a simple table "Names" with two columns: NameID and Name

    Your SQL Select Statement reads "SELECT NameID, Name FROM Names ORDER BY
    Name" and you have two records in it:
    ID=1, Name = "aaaa"
    ID=2, Name = "cccc"

    So, the first time you call the page, you get following grid:
    1 "aaaa" edit-button
    2 "cccc" edit-button

    during the time in which you are viewing this html page on your IE someone
    inserts another record in the table: "ID=3, Name='bbbb'".
    Then you click the edit button of the second row into your grid (2
    "cccc") intending to edit the name "cccc". When you klick the edit button,
    however, you get following grid:
    1 "aaaa" edit-button
    3 [bbbb] - updatable!!! Update-button, cancel-button
    2 "cccc" edit-button

    I am sure, you ghet what the reason is. What is the best solution to guard
    against this problem?

    Thank you for taking your time and understanding what I mean. I thought of a
    logical solution which however does not work. In case a discussion occur, I
    will write about it.

    All best

    Stamen


    Stamen Gortchev Guest

  2. Similar Questions and Discussions

    1. 20D a flawed camera?
      I've run into two people who had lock up problems, one person who had a weird problem where downloading long exposure images took as long as the...
    2. DB2 max shared memory limitation: 1.1 gigabytes? Where's the documentation? Flawed math?
      I heard DB2 32bit can only safely use up to 1.1 gigabytes of shared memory. I've summed up the ten DB2 memory components that utilize shared...
    3. #25566 [Bgs]: Casting of strings to integers is flawed, no checking for non numeric chars.
      ID: 25566 User updated by: Jared dot Williams1 at ntlworld dot com Reported By: Jared dot Williams1 at ntlworld dot com Status: ...
    4. #25566 [Opn->Bgs]: Casting of strings to integers is flawed, no checking for non numeric chars.
      ID: 25566 Updated by: rasmus@php.net Reported By: Jared dot Williams1 at ntlworld dot com -Status: Open +Status: Bogus Bug...
    5. #25566 [Opn]: Casting of strings to integers is flawed, no checking for non numeric chars.
      ID: 25566 User updated by: Jared dot Williams1 at ntlworld dot com -Summary: switch expressions seem to get cast to specific...
  3. #2

    Default Re: MSDN Examples flawed

    Stamen,

    Typically when doing an operation like this you wouldn't rebind the grid
    before the edit operation.

    So, in the page load sub use:

    If Not IsPostBack Then
    '---Bind your grid here
    End If

    (Make certain that viewstate is turned on for the grid. This way you don't
    have to rebind the grid.)

    Then rebind the grid after you edit the data.

    Sincerely,

    --
    S. Justin Gengo, MCP
    Web Developer

    Free code library at:
    [url]www.aboutfortunate.com[/url]

    "Out of chaos comes order."
    Nietzche


    "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    news:uuNuSR0gDHA.1648@TK2MSFTNGP10.phx.gbl...
    > Hi all,
    >
    > I think there is an inherent problem with most examples on the internet
    > (with MSDN, too!) showing datagrid's databinding. Here is, how they look
    > like:
    >
    > ========================
    > On Page_Load
    > if !IsPostBack: BindGrid()
    >
    > On_Edit
    > Set datagrid's EditItem to clicked item
    > BindGrid
    >
    > void BindGrid()
    > Fill DataSet through dataadapter
    > DataGrid.DataBind()
    > ========================
    >
    > Imagine a simple table "Names" with two columns: NameID and Name
    >
    > Your SQL Select Statement reads "SELECT NameID, Name FROM Names ORDER BY
    > Name" and you have two records in it:
    > ID=1, Name = "aaaa"
    > ID=2, Name = "cccc"
    >
    > So, the first time you call the page, you get following grid:
    > 1 "aaaa" edit-button
    > 2 "cccc" edit-button
    >
    > during the time in which you are viewing this html page on your IE someone
    > inserts another record in the table: "ID=3, Name='bbbb'".
    > Then you click the edit button of the second row into your grid (2
    > "cccc") intending to edit the name "cccc". When you klick the edit button,
    > however, you get following grid:
    > 1 "aaaa" edit-button
    > 3 [bbbb] - updatable!!! Update-button, cancel-button
    > 2 "cccc" edit-button
    >
    > I am sure, you ghet what the reason is. What is the best solution to guard
    > against this problem?
    >
    > Thank you for taking your time and understanding what I mean. I thought of
    a
    > logical solution which however does not work. In case a discussion occur,
    I
    > will write about it.
    >
    > All best
    >
    > Stamen
    >
    >

    S. Justin Gengo Guest

  4. #3

    Default Re: MSDN Examples flawed

    Hallo Justin,

    thanks for replying. What you propose however is exactly what I am doing:
    The code below is not immune against database changes:

    private void Page_Load(object sender, System.EventArgs e)
    {
    if (!IsPostBack)
    {
    this.da.Fill(ds1, "Countrys");
    this.DataGrid1.DataBind();
    }
    }

    private void DataGrid1_EditCommand(object source,
    System.Web.UI.WebControls.DataGridCommandEventArgs e)
    {
    this.da.Fill(ds1, "Names");
    DataGrid1.EditItemIndex = e.Item.ItemIndex;
    DataGrid1.DataBind();
    }

    What do you think about it?

    Thanks
    Stamen


    "S. Justin Gengo" <sjgengo@aboutfortunate.com> schrieb im Newsbeitrag
    news:eNuFsp2gDHA.2292@TK2MSFTNGP10.phx.gbl...
    > Stamen,
    >
    > Typically when doing an operation like this you wouldn't rebind the grid
    > before the edit operation.
    >
    > So, in the page load sub use:
    >
    > If Not IsPostBack Then
    > '---Bind your grid here
    > End If
    >
    > (Make certain that viewstate is turned on for the grid. This way you don't
    > have to rebind the grid.)
    >
    > Then rebind the grid after you edit the data.
    >
    > Sincerely,
    >
    > --
    > S. Justin Gengo, MCP
    > Web Developer
    >
    > Free code library at:
    > [url]www.aboutfortunate.com[/url]
    >
    > "Out of chaos comes order."
    > Nietzche
    >
    >
    > "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    > news:uuNuSR0gDHA.1648@TK2MSFTNGP10.phx.gbl...
    > > Hi all,
    > >
    > > I think there is an inherent problem with most examples on the internet
    > > (with MSDN, too!) showing datagrid's databinding. Here is, how they look
    > > like:
    > >
    > > ========================
    > > On Page_Load
    > > if !IsPostBack: BindGrid()
    > >
    > > On_Edit
    > > Set datagrid's EditItem to clicked item
    > > BindGrid
    > >
    > > void BindGrid()
    > > Fill DataSet through dataadapter
    > > DataGrid.DataBind()
    > > ========================
    > >
    > > Imagine a simple table "Names" with two columns: NameID and Name
    > >
    > > Your SQL Select Statement reads "SELECT NameID, Name FROM Names ORDER BY
    > > Name" and you have two records in it:
    > > ID=1, Name = "aaaa"
    > > ID=2, Name = "cccc"
    > >
    > > So, the first time you call the page, you get following grid:
    > > 1 "aaaa" edit-button
    > > 2 "cccc" edit-button
    > >
    > > during the time in which you are viewing this html page on your IE
    someone
    > > inserts another record in the table: "ID=3, Name='bbbb'".
    > > Then you click the edit button of the second row into your grid (2
    > > "cccc") intending to edit the name "cccc". When you klick the edit
    button,
    > > however, you get following grid:
    > > 1 "aaaa" edit-button
    > > 3 [bbbb] - updatable!!! Update-button, cancel-button
    > > 2 "cccc" edit-button
    > >
    > > I am sure, you ghet what the reason is. What is the best solution to
    guard
    > > against this problem?
    > >
    > > Thank you for taking your time and understanding what I mean. I thought
    of
    > a
    > > logical solution which however does not work. In case a discussion
    occur,
    > I
    > > will write about it.
    > >
    > > All best
    > >
    > > Stamen
    > >
    > >
    >
    >

    Stamen Gortchev Guest

  5. #4

    Default Re: MSDN Examples flawed

    "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    news:uuNuSR0gDHA.1648@TK2MSFTNGP10.phx.gbl...
    > Hi all,
    >
    > I think there is an inherent problem with most examples on the internet
    > (with MSDN, too!) showing datagrid's databinding. Here is, how they look
    > like:
    Could you please post a reference to an MSDN article which says you should
    reload the data from the database before the edit?
    --
    John Saunders
    Internet Engineer
    [email]john.saunders@surfcontrol.com[/email]


    John Saunders Guest

  6. #5

    Default Re: MSDN Examples flawed

    Stamen,

    As long as your entries have a primary key I don't see how they could be
    compromised. Of course any well designed database uses a primary key to make
    certain that a row is unique.

    Are the Id's that you are referring to not primary keys?

    Sincerely,

    --
    S. Justin Gengo, MCP
    Web Developer

    Free code library at:
    [url]www.aboutfortunate.com[/url]

    "Out of chaos comes order."
    Nietzche


    "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    news:ODSqq23gDHA.2124@TK2MSFTNGP12.phx.gbl...
    > Hallo Justin,
    >
    > thanks for replying. What you propose however is exactly what I am doing:
    > The code below is not immune against database changes:
    >
    > private void Page_Load(object sender, System.EventArgs e)
    > {
    > if (!IsPostBack)
    > {
    > this.da.Fill(ds1, "Countrys");
    > this.DataGrid1.DataBind();
    > }
    > }
    >
    > private void DataGrid1_EditCommand(object source,
    > System.Web.UI.WebControls.DataGridCommandEventArgs e)
    > {
    > this.da.Fill(ds1, "Names");
    > DataGrid1.EditItemIndex = e.Item.ItemIndex;
    > DataGrid1.DataBind();
    > }
    >
    > What do you think about it?
    >
    > Thanks
    > Stamen
    >
    >
    > "S. Justin Gengo" <sjgengo@aboutfortunate.com> schrieb im Newsbeitrag
    > news:eNuFsp2gDHA.2292@TK2MSFTNGP10.phx.gbl...
    > > Stamen,
    > >
    > > Typically when doing an operation like this you wouldn't rebind the grid
    > > before the edit operation.
    > >
    > > So, in the page load sub use:
    > >
    > > If Not IsPostBack Then
    > > '---Bind your grid here
    > > End If
    > >
    > > (Make certain that viewstate is turned on for the grid. This way you
    don't
    > > have to rebind the grid.)
    > >
    > > Then rebind the grid after you edit the data.
    > >
    > > Sincerely,
    > >
    > > --
    > > S. Justin Gengo, MCP
    > > Web Developer
    > >
    > > Free code library at:
    > > [url]www.aboutfortunate.com[/url]
    > >
    > > "Out of chaos comes order."
    > > Nietzche
    > >
    > >
    > > "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    > > news:uuNuSR0gDHA.1648@TK2MSFTNGP10.phx.gbl...
    > > > Hi all,
    > > >
    > > > I think there is an inherent problem with most examples on the
    internet
    > > > (with MSDN, too!) showing datagrid's databinding. Here is, how they
    look
    > > > like:
    > > >
    > > > ========================
    > > > On Page_Load
    > > > if !IsPostBack: BindGrid()
    > > >
    > > > On_Edit
    > > > Set datagrid's EditItem to clicked item
    > > > BindGrid
    > > >
    > > > void BindGrid()
    > > > Fill DataSet through dataadapter
    > > > DataGrid.DataBind()
    > > > ========================
    > > >
    > > > Imagine a simple table "Names" with two columns: NameID and Name
    > > >
    > > > Your SQL Select Statement reads "SELECT NameID, Name FROM Names ORDER
    BY
    > > > Name" and you have two records in it:
    > > > ID=1, Name = "aaaa"
    > > > ID=2, Name = "cccc"
    > > >
    > > > So, the first time you call the page, you get following grid:
    > > > 1 "aaaa" edit-button
    > > > 2 "cccc" edit-button
    > > >
    > > > during the time in which you are viewing this html page on your IE
    > someone
    > > > inserts another record in the table: "ID=3, Name='bbbb'".
    > > > Then you click the edit button of the second row into your grid (2
    > > > "cccc") intending to edit the name "cccc". When you klick the edit
    > button,
    > > > however, you get following grid:
    > > > 1 "aaaa" edit-button
    > > > 3 [bbbb] - updatable!!! Update-button, cancel-button
    > > > 2 "cccc" edit-button
    > > >
    > > > I am sure, you ghet what the reason is. What is the best solution to
    > guard
    > > > against this problem?
    > > >
    > > > Thank you for taking your time and understanding what I mean. I
    thought
    > of
    > > a
    > > > logical solution which however does not work. In case a discussion
    > occur,
    > > I
    > > > will write about it.
    > > >
    > > > All best
    > > >
    > > > Stamen
    > > >
    > > >
    > >
    > >
    >
    >

    S. Justin Gengo Guest

  7. #6

    Default Re: MSDN Examples flawed

    John,

    an example of Datagrid using can be found at:
    [url]http://msdn.microsoft.com/library/en-us/cpguide/html/cpconupdatingdatainsqldatabase.asp?frame=true[/url]

    Forget the Update event, concentrate on the Edit -it illustrates the point
    nicely.

    What they do is the following:
    They get the row number (for example 2) which should be edited from the
    datagrid's viewstate and set this row in the datagrid to be edited (row 2).
    then they re-read the data and rebind the grid. If, however, the newly
    reloaded data contains another row on that place (2) we get the
    inconsistency.

    I tried Auto generate columns=true, primary keys and so on... nothing
    wirks..

    Thanks
    Stamen

    "John Saunders" <john.saunders@surfcontrol.com> schrieb im Newsbeitrag
    news:u6aY564gDHA.696@TK2MSFTNGP09.phx.gbl...
    > "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    > news:uuNuSR0gDHA.1648@TK2MSFTNGP10.phx.gbl...
    > > Hi all,
    > >
    > > I think there is an inherent problem with most examples on the internet
    > > (with MSDN, too!) showing datagrid's databinding. Here is, how they look
    > > like:
    >
    > Could you please post a reference to an MSDN article which says you should
    > reload the data from the database before the edit?
    > --
    > John Saunders
    > Internet Engineer
    > [email]john.saunders@surfcontrol.com[/email]
    >
    >

    Stamen Gortchev Guest

  8. #7

    Default Re: MSDN Examples flawed

    Hi Justin,

    the table has two Columns: CountryID and Country - the sorting is done on
    Country not on CountryID, which of course is a primary key. The prblem of
    this approach is that it expects when refilling the datagrid that all
    records will come in the same order, what is quite an optimistic expectation
    in the general case.

    I tried your proposition of not refilling the dataadapter - it does not work
    at all, as now data gets shown on the repost.

    I had tried another approach:

    On_Edit_Event
    set editIndex=clickedIndex
    Exit

    hoping that the grid gets reloaded from the ViewState. Unfortunately this
    does not work for some reason: The first time i click [Edit], nothing
    happens. The second time I click - the record enters edit-state wehich I
    have clicked the first time - so there is something like a "one click lag".
    Therefore i think that the event comes up too late - when the grid has
    already been initialized or somethink like that..:-(

    That's it! The most rigorous approach seems to be like this:

    In the edit_event, read the id of the data reord (CountryID). Refill the
    Grid. Find the row containing the data record with the found ID. Set this
    row in Edit mode. But it beats the purpose of ViewState and all..

    Sorry for the long message

    Cheers

    Stamen



    "S. Justin Gengo" <sjgengo@aboutfortunate.com> schrieb im Newsbeitrag
    news:%23D14Ha6gDHA.1700@TK2MSFTNGP10.phx.gbl...
    > Stamen,
    >
    > As long as your entries have a primary key I don't see how they could be
    > compromised. Of course any well designed database uses a primary key to
    make
    > certain that a row is unique.
    >
    > Are the Id's that you are referring to not primary keys?
    >
    > Sincerely,
    >
    > --
    > S. Justin Gengo, MCP
    > Web Developer
    >
    > Free code library at:
    > [url]www.aboutfortunate.com[/url]
    >
    > "Out of chaos comes order."
    > Nietzche
    >
    >
    > "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    > news:ODSqq23gDHA.2124@TK2MSFTNGP12.phx.gbl...
    > > Hallo Justin,
    > >
    > > thanks for replying. What you propose however is exactly what I am
    doing:
    > > The code below is not immune against database changes:
    > >
    > > private void Page_Load(object sender, System.EventArgs e)
    > > {
    > > if (!IsPostBack)
    > > {
    > > this.da.Fill(ds1, "Countrys");
    > > this.DataGrid1.DataBind();
    > > }
    > > }
    > >
    > > private void DataGrid1_EditCommand(object source,
    > > System.Web.UI.WebControls.DataGridCommandEventArgs e)
    > > {
    > > this.da.Fill(ds1, "Names");
    > > DataGrid1.EditItemIndex = e.Item.ItemIndex;
    > > DataGrid1.DataBind();
    > > }
    > >
    > > What do you think about it?
    > >
    > > Thanks
    > > Stamen
    > >
    > >
    > > "S. Justin Gengo" <sjgengo@aboutfortunate.com> schrieb im Newsbeitrag
    > > news:eNuFsp2gDHA.2292@TK2MSFTNGP10.phx.gbl...
    > > > Stamen,
    > > >
    > > > Typically when doing an operation like this you wouldn't rebind the
    grid
    > > > before the edit operation.
    > > >
    > > > So, in the page load sub use:
    > > >
    > > > If Not IsPostBack Then
    > > > '---Bind your grid here
    > > > End If
    > > >
    > > > (Make certain that viewstate is turned on for the grid. This way you
    > don't
    > > > have to rebind the grid.)
    > > >
    > > > Then rebind the grid after you edit the data.
    > > >
    > > > Sincerely,
    > > >
    > > > --
    > > > S. Justin Gengo, MCP
    > > > Web Developer
    > > >
    > > > Free code library at:
    > > > [url]www.aboutfortunate.com[/url]
    > > >
    > > > "Out of chaos comes order."
    > > > Nietzche
    > > >
    > > >
    > > > "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    > > > news:uuNuSR0gDHA.1648@TK2MSFTNGP10.phx.gbl...
    > > > > Hi all,
    > > > >
    > > > > I think there is an inherent problem with most examples on the
    > internet
    > > > > (with MSDN, too!) showing datagrid's databinding. Here is, how they
    > look
    > > > > like:
    > > > >
    > > > > ========================
    > > > > On Page_Load
    > > > > if !IsPostBack: BindGrid()
    > > > >
    > > > > On_Edit
    > > > > Set datagrid's EditItem to clicked item
    > > > > BindGrid
    > > > >
    > > > > void BindGrid()
    > > > > Fill DataSet through dataadapter
    > > > > DataGrid.DataBind()
    > > > > ========================
    > > > >
    > > > > Imagine a simple table "Names" with two columns: NameID and Name
    > > > >
    > > > > Your SQL Select Statement reads "SELECT NameID, Name FROM Names
    ORDER
    > BY
    > > > > Name" and you have two records in it:
    > > > > ID=1, Name = "aaaa"
    > > > > ID=2, Name = "cccc"
    > > > >
    > > > > So, the first time you call the page, you get following grid:
    > > > > 1 "aaaa" edit-button
    > > > > 2 "cccc" edit-button
    > > > >
    > > > > during the time in which you are viewing this html page on your IE
    > > someone
    > > > > inserts another record in the table: "ID=3, Name='bbbb'".
    > > > > Then you click the edit button of the second row into your grid (2
    > > > > "cccc") intending to edit the name "cccc". When you klick the edit
    > > button,
    > > > > however, you get following grid:
    > > > > 1 "aaaa" edit-button
    > > > > 3 [bbbb] - updatable!!! Update-button, cancel-button
    > > > > 2 "cccc" edit-button
    > > > >
    > > > > I am sure, you ghet what the reason is. What is the best solution to
    > > guard
    > > > > against this problem?
    > > > >
    > > > > Thank you for taking your time and understanding what I mean. I
    > thought
    > > of
    > > > a
    > > > > logical solution which however does not work. In case a discussion
    > > occur,
    > > > I
    > > > > will write about it.
    > > > >
    > > > > All best
    > > > >
    > > > > Stamen
    > > > >
    > > > >
    > > >
    > > >
    > >
    > >
    >
    >

    Stamen Gortchev Guest

  9. #8

    Default Re: MSDN Examples flawed

    Stamen,

    In the example I emailed to you I forgot to tell you to also remove the
    databind. Of course if you databind to an empty dataset your grid will be
    blank.

    You should be making certain that the datagrid itself has it's viewstate set
    to true (as should any object it may be contained in such as a panel and the
    page object.

    Then your code should simply set that row to be editable:

    private void DataGrid1_EditCommand(object source,
    System.Web.UI.WebControls.DataGridCommandEventArgs e)
    {
    DataGrid1.EditItemIndex = e.Item.ItemIndex;
    }

    Since the datagrid is now not being repopulated from the database it will
    only contain the original data and thus no problem...

    Sincerely,

    --
    S. Justin Gengo, MCP
    Web Developer

    Free code library at:
    [url]www.aboutfortunate.com[/url]

    "Out of chaos comes order."
    Nietzche


    "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    news:ODSqq23gDHA.2124@TK2MSFTNGP12.phx.gbl...
    > Hallo Justin,
    >
    > thanks for replying. What you propose however is exactly what I am doing:
    > The code below is not immune against database changes:
    >
    > private void Page_Load(object sender, System.EventArgs e)
    > {
    > if (!IsPostBack)
    > {
    > this.da.Fill(ds1, "Countrys");
    > this.DataGrid1.DataBind();
    > }
    > }
    >
    > private void DataGrid1_EditCommand(object source,
    > System.Web.UI.WebControls.DataGridCommandEventArgs e)
    > {
    > this.da.Fill(ds1, "Names");
    > DataGrid1.EditItemIndex = e.Item.ItemIndex;
    > DataGrid1.DataBind();
    > }
    >
    > What do you think about it?
    >
    > Thanks
    > Stamen
    >
    >
    > "S. Justin Gengo" <sjgengo@aboutfortunate.com> schrieb im Newsbeitrag
    > news:eNuFsp2gDHA.2292@TK2MSFTNGP10.phx.gbl...
    > > Stamen,
    > >
    > > Typically when doing an operation like this you wouldn't rebind the grid
    > > before the edit operation.
    > >
    > > So, in the page load sub use:
    > >
    > > If Not IsPostBack Then
    > > '---Bind your grid here
    > > End If
    > >
    > > (Make certain that viewstate is turned on for the grid. This way you
    don't
    > > have to rebind the grid.)
    > >
    > > Then rebind the grid after you edit the data.
    > >
    > > Sincerely,
    > >
    > > --
    > > S. Justin Gengo, MCP
    > > Web Developer
    > >
    > > Free code library at:
    > > [url]www.aboutfortunate.com[/url]
    > >
    > > "Out of chaos comes order."
    > > Nietzche
    > >
    > >
    > > "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    > > news:uuNuSR0gDHA.1648@TK2MSFTNGP10.phx.gbl...
    > > > Hi all,
    > > >
    > > > I think there is an inherent problem with most examples on the
    internet
    > > > (with MSDN, too!) showing datagrid's databinding. Here is, how they
    look
    > > > like:
    > > >
    > > > ========================
    > > > On Page_Load
    > > > if !IsPostBack: BindGrid()
    > > >
    > > > On_Edit
    > > > Set datagrid's EditItem to clicked item
    > > > BindGrid
    > > >
    > > > void BindGrid()
    > > > Fill DataSet through dataadapter
    > > > DataGrid.DataBind()
    > > > ========================
    > > >
    > > > Imagine a simple table "Names" with two columns: NameID and Name
    > > >
    > > > Your SQL Select Statement reads "SELECT NameID, Name FROM Names ORDER
    BY
    > > > Name" and you have two records in it:
    > > > ID=1, Name = "aaaa"
    > > > ID=2, Name = "cccc"
    > > >
    > > > So, the first time you call the page, you get following grid:
    > > > 1 "aaaa" edit-button
    > > > 2 "cccc" edit-button
    > > >
    > > > during the time in which you are viewing this html page on your IE
    > someone
    > > > inserts another record in the table: "ID=3, Name='bbbb'".
    > > > Then you click the edit button of the second row into your grid (2
    > > > "cccc") intending to edit the name "cccc". When you klick the edit
    > button,
    > > > however, you get following grid:
    > > > 1 "aaaa" edit-button
    > > > 3 [bbbb] - updatable!!! Update-button, cancel-button
    > > > 2 "cccc" edit-button
    > > >
    > > > I am sure, you ghet what the reason is. What is the best solution to
    > guard
    > > > against this problem?
    > > >
    > > > Thank you for taking your time and understanding what I mean. I
    thought
    > of
    > > a
    > > > logical solution which however does not work. In case a discussion
    > occur,
    > > I
    > > > will write about it.
    > > >
    > > > All best
    > > >
    > > > Stamen
    > > >
    > > >
    > >
    > >
    >
    >

    S. Justin Gengo Guest

  10. #9

    Default Re: MSDN Examples flawed

    Stamen,

    In the example I emailed to you I forgot to tell you to also remove the
    databind. Of course if you databind to an empty dataset your grid will be
    blank.

    You should be making certain that the datagrid itself has it's viewstate set
    to true (as should any object it may be contained in such as a panel and the
    page object. The datagrid should certainly re-populate itself from
    viewstate. If it doesn't then something else is wrong with your code.

    Then your code should simply set that row to be editable:

    private void DataGrid1_EditCommand(object source,
    System.Web.UI.WebControls.DataGridCommandEventArgs e)
    {
    DataGrid1.EditItemIndex = e.Item.ItemIndex;
    }

    Since the datagrid is now not being repopulated from the database it will
    only contain the original data and thus no problem...

    Sincerely,

    --
    S. Justin Gengo, MCP
    Web Developer

    Free code library at:
    [url]www.aboutfortunate.com[/url]

    "Out of chaos comes order."
    Nietzche


    "Stamen Gortchev" <nospam@nospam.de> wrote in message
    news:O%234eAYChDHA.1048@TK2MSFTNGP11.phx.gbl...
    > Hi Justin,
    >
    > the table has two Columns: CountryID and Country - the sorting is done on
    > Country not on CountryID, which of course is a primary key. The prblem of
    > this approach is that it expects when refilling the datagrid that all
    > records will come in the same order, what is quite an optimistic
    expectation
    > in the general case.
    >
    > I tried your proposition of not refilling the dataadapter - it does not
    work
    > at all, as now data gets shown on the repost.
    >
    > I had tried another approach:
    >
    > On_Edit_Event
    > set editIndex=clickedIndex
    > Exit
    >
    > hoping that the grid gets reloaded from the ViewState. Unfortunately this
    > does not work for some reason: The first time i click [Edit], nothing
    > happens. The second time I click - the record enters edit-state wehich I
    > have clicked the first time - so there is something like a "one click
    lag".
    > Therefore i think that the event comes up too late - when the grid has
    > already been initialized or somethink like that..:-(
    >
    > That's it! The most rigorous approach seems to be like this:
    >
    > In the edit_event, read the id of the data reord (CountryID). Refill the
    > Grid. Find the row containing the data record with the found ID. Set this
    > row in Edit mode. But it beats the purpose of ViewState and all..
    >
    > Sorry for the long message
    >
    > Cheers
    >
    > Stamen
    >
    >
    >
    > "S. Justin Gengo" <sjgengo@aboutfortunate.com> schrieb im Newsbeitrag
    > news:%23D14Ha6gDHA.1700@TK2MSFTNGP10.phx.gbl...
    > > Stamen,
    > >
    > > As long as your entries have a primary key I don't see how they could be
    > > compromised. Of course any well designed database uses a primary key to
    > make
    > > certain that a row is unique.
    > >
    > > Are the Id's that you are referring to not primary keys?
    > >
    > > Sincerely,
    > >
    > > --
    > > S. Justin Gengo, MCP
    > > Web Developer
    > >
    > > Free code library at:
    > > [url]www.aboutfortunate.com[/url]
    > >
    > > "Out of chaos comes order."
    > > Nietzche
    > >
    > >
    > > "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    > > news:ODSqq23gDHA.2124@TK2MSFTNGP12.phx.gbl...
    > > > Hallo Justin,
    > > >
    > > > thanks for replying. What you propose however is exactly what I am
    > doing:
    > > > The code below is not immune against database changes:
    > > >
    > > > private void Page_Load(object sender, System.EventArgs e)
    > > > {
    > > > if (!IsPostBack)
    > > > {
    > > > this.da.Fill(ds1, "Countrys");
    > > > this.DataGrid1.DataBind();
    > > > }
    > > > }
    > > >
    > > > private void DataGrid1_EditCommand(object source,
    > > > System.Web.UI.WebControls.DataGridCommandEventArgs e)
    > > > {
    > > > this.da.Fill(ds1, "Names");
    > > > DataGrid1.EditItemIndex = e.Item.ItemIndex;
    > > > DataGrid1.DataBind();
    > > > }
    > > >
    > > > What do you think about it?
    > > >
    > > > Thanks
    > > > Stamen
    > > >
    > > >
    > > > "S. Justin Gengo" <sjgengo@aboutfortunate.com> schrieb im Newsbeitrag
    > > > news:eNuFsp2gDHA.2292@TK2MSFTNGP10.phx.gbl...
    > > > > Stamen,
    > > > >
    > > > > Typically when doing an operation like this you wouldn't rebind the
    > grid
    > > > > before the edit operation.
    > > > >
    > > > > So, in the page load sub use:
    > > > >
    > > > > If Not IsPostBack Then
    > > > > '---Bind your grid here
    > > > > End If
    > > > >
    > > > > (Make certain that viewstate is turned on for the grid. This way you
    > > don't
    > > > > have to rebind the grid.)
    > > > >
    > > > > Then rebind the grid after you edit the data.
    > > > >
    > > > > Sincerely,
    > > > >
    > > > > --
    > > > > S. Justin Gengo, MCP
    > > > > Web Developer
    > > > >
    > > > > Free code library at:
    > > > > [url]www.aboutfortunate.com[/url]
    > > > >
    > > > > "Out of chaos comes order."
    > > > > Nietzche
    > > > >
    > > > >
    > > > > "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    > > > > news:uuNuSR0gDHA.1648@TK2MSFTNGP10.phx.gbl...
    > > > > > Hi all,
    > > > > >
    > > > > > I think there is an inherent problem with most examples on the
    > > internet
    > > > > > (with MSDN, too!) showing datagrid's databinding. Here is, how
    they
    > > look
    > > > > > like:
    > > > > >
    > > > > > ========================
    > > > > > On Page_Load
    > > > > > if !IsPostBack: BindGrid()
    > > > > >
    > > > > > On_Edit
    > > > > > Set datagrid's EditItem to clicked item
    > > > > > BindGrid
    > > > > >
    > > > > > void BindGrid()
    > > > > > Fill DataSet through dataadapter
    > > > > > DataGrid.DataBind()
    > > > > > ========================
    > > > > >
    > > > > > Imagine a simple table "Names" with two columns: NameID and Name
    > > > > >
    > > > > > Your SQL Select Statement reads "SELECT NameID, Name FROM Names
    > ORDER
    > > BY
    > > > > > Name" and you have two records in it:
    > > > > > ID=1, Name = "aaaa"
    > > > > > ID=2, Name = "cccc"
    > > > > >
    > > > > > So, the first time you call the page, you get following grid:
    > > > > > 1 "aaaa" edit-button
    > > > > > 2 "cccc" edit-button
    > > > > >
    > > > > > during the time in which you are viewing this html page on your IE
    > > > someone
    > > > > > inserts another record in the table: "ID=3, Name='bbbb'".
    > > > > > Then you click the edit button of the second row into your grid (2
    > > > > > "cccc") intending to edit the name "cccc". When you klick the edit
    > > > button,
    > > > > > however, you get following grid:
    > > > > > 1 "aaaa" edit-button
    > > > > > 3 [bbbb] - updatable!!! Update-button, cancel-button
    > > > > > 2 "cccc" edit-button
    > > > > >
    > > > > > I am sure, you ghet what the reason is. What is the best solution
    to
    > > > guard
    > > > > > against this problem?
    > > > > >
    > > > > > Thank you for taking your time and understanding what I mean. I
    > > thought
    > > > of
    > > > > a
    > > > > > logical solution which however does not work. In case a discussion
    > > > occur,
    > > > > I
    > > > > > will write about it.
    > > > > >
    > > > > > All best
    > > > > >
    > > > > > Stamen
    > > > > >
    > > > > >
    > > > >
    > > > >
    > > >
    > > >
    > >
    > >
    >
    >

    S. Justin Gengo Guest

  11. #10

    Default Re: MSDN Examples flawed

    "Stamen Gortchev" <nospam@nospam.de> wrote in message
    news:O%234eAYChDHA.1048@TK2MSFTNGP11.phx.gbl...
    > Hi Justin,
    >
    > the table has two Columns: CountryID and Country - the sorting is done on
    > Country not on CountryID, which of course is a primary key. The prblem of
    > this approach is that it expects when refilling the datagrid that all
    > records will come in the same order, what is quite an optimistic
    expectation
    > in the general case.
    >
    > I tried your proposition of not refilling the dataadapter - it does not
    work
    > at all, as now data gets shown on the repost.
    >
    > I had tried another approach:
    >
    > On_Edit_Event
    > set editIndex=clickedIndex
    > Exit
    Try calling DataGrid.DataBind after you set EditItemIndex.
    --
    John Saunders
    Internet Engineer
    [email]john.saunders@surfcontrol.com[/email]


    John Saunders Guest

  12. #11

    Default Re: MSDN Examples flawed

    "Stamen Gortchev" <nospam@nospam.de> wrote in message
    news:OLSemXAhDHA.2544@TK2MSFTNGP12.phx.gbl...
    > John,
    >
    > an example of Datagrid using can be found at:
    >
    [url]http://msdn.microsoft.com/library/en-us/cpguide/html/cpconupdatingdatainsqldatabase.asp?frame=true[/url]

    Stamen,

    I took a look at that link, you're correct - that's a bug.

    I submitted the issue to Microsoft by clicking the "feedback" link at the
    bottom of the page. I got a response saying they'll look into correcting it
    in future documentation. I was also told that the same pattern is used in
    several places in the documentation and in the QuickStarts, and that the
    issue will be raised for both.

    I've had good response from the Microsoft Documentation and Training people
    when I've commented on the MSDN documentation. I've always received a
    prompt, courteous and even intelligent response. I haven't seen the results
    in the documentation yet, but I'll be checking when the 2.0 documentation
    comes out. : -)
    --
    John Saunders
    Internet Engineer
    [email]john.saunders@surfcontrol.com[/email]


    John Saunders Guest

  13. #12

    Default Re: MSDN Examples flawed

    Justin,

    sorry for the late response - I only use newsgroups from work..

    I know what you mean and I have tried it. Unfortunately, I still have that
    "one-click-delay". All I do is this:
    I pul a dataadapter on my Webform, fill dataset and bind it to a datagrid
    (all done with my mouse). Then in the page_load event I call
    If not ispostback
    dataadapter.fill (ds, tablename)
    datagrid.databind

    And the Edit-event is the way you tell me. And it is still not
    working..:-( I do not tamper with the viewstate of neither element as per
    default it is always set to true, isn't it? I use VS2003.

    If you think I foget something, can you please send me a small example where
    it works - I hope it would be interesting for you to try it for yourself and
    then ou can perhaps email it to me. I will write you an email in order not
    to get thousands of virus mails into my mailbox.

    Thanks again

    Stamen

    "S. Justin Gengo" <sjgengo@aboutfortunate.com> schrieb im Newsbeitrag
    news:O8oDGEDhDHA.2544@TK2MSFTNGP12.phx.gbl...
    > Stamen,
    >
    > In the example I emailed to you I forgot to tell you to also remove the
    > databind. Of course if you databind to an empty dataset your grid will be
    > blank.
    >
    > You should be making certain that the datagrid itself has it's viewstate
    set
    > to true (as should any object it may be contained in such as a panel and
    the
    > page object.
    >
    > Then your code should simply set that row to be editable:
    >
    > private void DataGrid1_EditCommand(object source,
    > System.Web.UI.WebControls.DataGridCommandEventArgs e)
    > {
    > DataGrid1.EditItemIndex = e.Item.ItemIndex;
    > }
    >
    > Since the datagrid is now not being repopulated from the database it will
    > only contain the original data and thus no problem...
    >
    > Sincerely,
    >
    > --
    > S. Justin Gengo, MCP
    > Web Developer
    >
    > Free code library at:
    > [url]www.aboutfortunate.com[/url]
    >
    > "Out of chaos comes order."
    > Nietzche
    >
    >
    > "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    > news:ODSqq23gDHA.2124@TK2MSFTNGP12.phx.gbl...
    > > Hallo Justin,
    > >
    > > thanks for replying. What you propose however is exactly what I am
    doing:
    > > The code below is not immune against database changes:
    > >
    > > private void Page_Load(object sender, System.EventArgs e)
    > > {
    > > if (!IsPostBack)
    > > {
    > > this.da.Fill(ds1, "Countrys");
    > > this.DataGrid1.DataBind();
    > > }
    > > }
    > >
    > > private void DataGrid1_EditCommand(object source,
    > > System.Web.UI.WebControls.DataGridCommandEventArgs e)
    > > {
    > > this.da.Fill(ds1, "Names");
    > > DataGrid1.EditItemIndex = e.Item.ItemIndex;
    > > DataGrid1.DataBind();
    > > }
    > >
    > > What do you think about it?
    > >
    > > Thanks
    > > Stamen
    > >
    > >
    > > "S. Justin Gengo" <sjgengo@aboutfortunate.com> schrieb im Newsbeitrag
    > > news:eNuFsp2gDHA.2292@TK2MSFTNGP10.phx.gbl...
    > > > Stamen,
    > > >
    > > > Typically when doing an operation like this you wouldn't rebind the
    grid
    > > > before the edit operation.
    > > >
    > > > So, in the page load sub use:
    > > >
    > > > If Not IsPostBack Then
    > > > '---Bind your grid here
    > > > End If
    > > >
    > > > (Make certain that viewstate is turned on for the grid. This way you
    > don't
    > > > have to rebind the grid.)
    > > >
    > > > Then rebind the grid after you edit the data.
    > > >
    > > > Sincerely,
    > > >
    > > > --
    > > > S. Justin Gengo, MCP
    > > > Web Developer
    > > >
    > > > Free code library at:
    > > > [url]www.aboutfortunate.com[/url]
    > > >
    > > > "Out of chaos comes order."
    > > > Nietzche
    > > >
    > > >
    > > > "Stamen Gortchev" <s.gortchev@onventis.de> wrote in message
    > > > news:uuNuSR0gDHA.1648@TK2MSFTNGP10.phx.gbl...
    > > > > Hi all,
    > > > >
    > > > > I think there is an inherent problem with most examples on the
    > internet
    > > > > (with MSDN, too!) showing datagrid's databinding. Here is, how they
    > look
    > > > > like:
    > > > >
    > > > > ========================
    > > > > On Page_Load
    > > > > if !IsPostBack: BindGrid()
    > > > >
    > > > > On_Edit
    > > > > Set datagrid's EditItem to clicked item
    > > > > BindGrid
    > > > >
    > > > > void BindGrid()
    > > > > Fill DataSet through dataadapter
    > > > > DataGrid.DataBind()
    > > > > ========================
    > > > >
    > > > > Imagine a simple table "Names" with two columns: NameID and Name
    > > > >
    > > > > Your SQL Select Statement reads "SELECT NameID, Name FROM Names
    ORDER
    > BY
    > > > > Name" and you have two records in it:
    > > > > ID=1, Name = "aaaa"
    > > > > ID=2, Name = "cccc"
    > > > >
    > > > > So, the first time you call the page, you get following grid:
    > > > > 1 "aaaa" edit-button
    > > > > 2 "cccc" edit-button
    > > > >
    > > > > during the time in which you are viewing this html page on your IE
    > > someone
    > > > > inserts another record in the table: "ID=3, Name='bbbb'".
    > > > > Then you click the edit button of the second row into your grid (2
    > > > > "cccc") intending to edit the name "cccc". When you klick the edit
    > > button,
    > > > > however, you get following grid:
    > > > > 1 "aaaa" edit-button
    > > > > 3 [bbbb] - updatable!!! Update-button, cancel-button
    > > > > 2 "cccc" edit-button
    > > > >
    > > > > I am sure, you ghet what the reason is. What is the best solution to
    > > guard
    > > > > against this problem?
    > > > >
    > > > > Thank you for taking your time and understanding what I mean. I
    > thought
    > > of
    > > > a
    > > > > logical solution which however does not work. In case a discussion
    > > occur,
    > > > I
    > > > > will write about it.
    > > > >
    > > > > All best
    > > > >
    > > > > Stamen
    > > > >
    > > > >
    > > >
    > > >
    > >
    > >
    >
    >

    Stamen Gortchev Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139