Chapter 13 p.443 Try it out

sycomputing · July 1st, 2010, 02:17 PM

I drop a DetailsView according to the instructions.

At Step 5 I set the DefaultMode as instructed, however, I notice the code doesn't setup the asp:BoundFields as in the example in the book. It looks like this after the Behavior property is set:

Code:

<asp:DetailsView ID="DetailsView1" runat="server" DataSourceID="SqlDataSource1" 
    DefaultMode="Insert" Height="50px" Width="125px">
    <Fields>
      <asp:CommandField ShowInsertButton="True" />
    </Fields>
  </asp:DetailsView>

Obviously, when the page is run the Id column of the sql table is insertable, which we don't want.

This isn't a big deal as I get how to fix it, I was just wondering what, if anything, I could be doing wrong here. The instructions seem clear enough and I've tried them twice.

I wouldn't mind having the opportunity to be lazy by not having to write the additional lines to configure the asp:BoundFields manually in cases where larger amounts of data are at play.

I also notice that the "AutoGenerateRows=False" and the "DataKeyNames=Id" properties aren't set in my code vs the code example in the book...maybe I have to set these manually every time? The books seems to suggest these properties will be autoset after pointing the control to the SqlDataSource control.
Thanks for your help.

Imar · July 2nd, 2010, 03:45 AM

I don't know why; that sometimes happens. I think it's a bug. What you see in the book is how it's supposed to work, and how it quite often, but not always works.

Another possible cause for this problem is that you forgot to turn the Id column of the table into an identity and primary key column.

Cheers,

Imar

sycomputing · July 2nd, 2010, 06:14 PM

Bah...it's happening in the Chapter 14 p.499 try it out as well and the page doesn't work correctly.

Code:

<asp:DetailsView ID="DetailsView1" runat="server" 
    DataSourceID="EntityDataSource1" DefaultMode="Insert" Height="50px" 
    Width="125px">
    <Fields>
      <asp:CommandField ShowInsertButton="True" />
    </Fields>
  </asp:DetailsView>

My table id assignments and keys are correct...bummer.

Would someone mind posting the correct code for this Try it Out?

sycomputing · July 2nd, 2010, 06:27 PM

Ok I got it to work.

Instead of deleting the control and starting from the beginning this time, I left the control there and just ran through steps 6 - 13 again.

Maybe I didn't do something correctly the first time.

Imar · July 3rd, 2010, 08:39 AM

Quote:

Just curious, after I do the test insert at step 13 of this chapter, I open the table to look at the data and notice the new entry has an Id of 3.
Why isn't it 1? There have been no other entries in the table. It's brand new.

IDs are handed out by the database not only when a record is inserted successfully, butt sometimes also when an insert fails.
So, for example if you insert a record in the Pictures table with a reference to an AlbumId that does not exist in the Albums table, the insert fails and the record is not inserted in Pictures, but its identity may be increased nonetheless.

Cheers,

Imar