You'll find that the appearance and behavior of the Template Fields is identical to the experience when Bound Fields were used instead.
While the default editing and inserting interfaces for the Bound Field and Check Box Field can be helpful, the interface lacks any sort of validation.
If a user makes a data entry mistake - such as omitting the (such as -50) an exception will be raised from within the depths of the application architecture.
There, select each of the Bound Fields and click the "Convert this field into a Template Field" link.
Figure 3: Convert Each of the Details View's and Grid View's Bound Fields Into Template Fields (Click to view full-size image) Converting a Bound Field into a Template Field through the Fields dialog box generates a Template Field that exhibits the same read-only, editing, and inserting interfaces as the Bound Field itself.
A common way to use these collections is to HTML-encode the values supplied by the user before they are stored in the data source.
string connetion String = "YOUR_CONSTR" ; string upd Stmt = "UPDATE Quantity set [email protected]_pro4, [email protected]_pro5, [email protected]_profile5 " "where [email protected] Name"; using (Sql Connection cnn = new Sql Connection(connetion String)) I don't see any instance of Sql Connection created!?
Additionally, the page included a Details View whose , thereby always rendering in insert mode.
From this Details View, the user could enter the name and price for a new product, click Insert, and have it added to the system (see Figure 1).
Similarly, when inserting a new record into a Details View control, those Bound Fields whose (the default) are rendered as empty textboxes, into which the user can provide the new record's field values.