Common field events and results different relationship and processing

in ASP. NET development, maybe we need to add, search or do updates in a common field domain. The other Ammonium button events are also separate separately. Events do not handle the same results. This requires that the relationship and results between them be reconciled in an ASPX Web page.
If online users also asked similar questions:

Insus.net this as a small case, simple to do a demonstration, for your reference. Prepare the database First:

SQL Source:

CREATE TABLE [T1]([col1] NVARCHAR( -),[col2] NVARCHAR( -))GOCREATE PROCEDURE [dbo].[Usp_t1_insert](    @col1 NVARCHAR( -),    @col2 NVARCHAR( -)) asINSERT  into [dbo].[T1]([col1],[col2])VALUES(@col1,@col2)GOCREATE PROCEDURE [dbo].[Usp_t1_getall] asSELECT [col1],[col2]  from [dbo].[T1] GOCREATE PROCEDURE [dbo].[Usp_t1_search](    @col1 NVARCHAR( -),    @col2 NVARCHAR( -)) asSELECT [col1],[col2]  from [dbo].[T1] WHERE [col1]  like '%'+@col1 +'%'  and [col2]  like '%'+@col2 +'%'GO

View Code

Prepare the file or interface on the website in the following order:



Demonstrate:

Weibo will take the focus and simplification, the code is a different, you can directly download from the following link:
Http://download.cnblogs.com/insus/ASPDOTNET/DyFieldAspxUcInterface.rar

From this blog post, you will learn about the collaboration between ASPX and user control ascx, how to load statically, and dynamically load, how to set properties, assign values, and get values. The assignment of dynamic loading will be handled, and will be applied when developing ASP. The other interface (interface) does play an important role between multiple controls.

Common field events and results different relationship and processing