The detailsview detailsview1 fired event itemupdating which

It s fairly common for Web applications to work on a single record at a time.For example, displaying the contents of a single record of data is a necessary practice when you build master/detail views. NET 2.0, the Details View control renders a single record at a time from its associated data source, optionally providing paging buttons to navigate between records and Create/Read/Update/Delete (CRUD) capabilities.To work through this example, you will need a SQL Server database with a table named Photos. Table 2: Schema of Photos table Notice that you have used the varbinary(MAX) data type for Photo column instead of the traditional Image data type.You will now develop a web site that allows the users to add, modify, and delete individual records of the Photos table. If you wish, you can add a new database to its App_Data folder to create the Photos table. Listing 1: Properties of Photo class The Photo class has four public properties: Photo ID, Title, Description, and Photo Data.After doing this, we can retrieve the Data Key value in the following ways. So, we call Databind() method in the Page Index Changed event handler and then retrieve the datakey value as shown in the code given below. The code to retrieve Data Key value in the Data Bound event of details View control is given below.These features are provided out-of-the-box and are not configurable by programmers.Or, at least, not declaratively and, maybe, not easily.

The Value property of the photo parameter holds a byte array containing the photo data.

In this column, I ll first answer a specific question posed by a reader, then move on to putting the solution in perspective and extending other features of the Details View control.

Let s say you need a Web page that collects data and populates a database.

Storing BLOBs directly inside SQL server provides the following advantages: In summary, depending on the application being developed, you should decide whether storing BLOB data in SQL Server is the way to go. To read BLOB data, you need to use the Sql Data Reader class of ADO. The use of Sql Data Reader class to read BLOB data can be best understood with an example.

That said, generally CMS systems, photo albums, slide show applications, document management systems, and so forth are good candidates for storing BLOBs inside SQL Server. You will develop a simple application that manages photos stored in a SQL Server database.