ASP. NET Web development framework-4 Query

Enterprise Solution supports user-defined query and lookup, and defines query as a standard function. lookup is used to return the query value to the data input form.

First, configure the database connection string and use the company registration to register a new database connection. In the query designer, select the corresponding object and design the association. The Web framework can parse the query and turn it into a page function.

Add a TriggerBox on the customer page. A small icon is displayed at the end of it to search for data.

 
 

  
  
 <ext:TriggerBox ID="tbxCustomerNo" ShowLabel="true" Readonly="false" TriggerIcon="Search" 
  
  
                            OnTriggerClick="tbxCustomerNo_TriggerClick" OnTextChanged="tbxCustomerNo_TextChanged" 
  
  
                            AutoPostBack="true" Label="Customer No." runat="server" Lookup="CustomerEntryLookup" 
  
  
                            DataBindingString="CustomerEntity:CustomerNo">  
  
  
</ext:TriggerBox> 
 
 

Let's look at the background code processing mode.

 
 

  
  
string lookup = tbxCustomerNo.Lookup;  
  
  
             tbxCustomerNo.OnClientTriggerClick = Window1.GetSaveStateReference(tbxCustomerNo.ClientID, HiddenField1.ClientID, HiddenField2.ClientID)  
  
  
               + Window1.GetShowReference(string.Format("lookup.aspx?id={0}", lookup), "Look-up:Customer"); 
 
 

From the preceding Web page, the Lookup attribute is mermerentrylookup. This statement associates Lookup with Window1 of the page for the pop-up window. At the same time, it specifies the HiddenField1 of the page to accept the return value of Lookup. Finally, it calls the re-sending and refresh process of the window, page refresh. The Code is as follows:

 
 

  
  
protected void Window1_Close(object sender, EventArgs e)  
  
  
{  
  
  
            string customerNo = tbxCustomerNo.Text;  
  
  
            if (!string.IsNullOrWhiteSpace(customerNo))  
  
  
            {  
  
  
                ReloadEntity(customerNo);              
  
  
            }  
  
  
}     
 
 

In this way, the selection value is displayed on the query page, the return value is returned to the main form, and the main form is refreshed.

Let's take a look at lookup. how is the aspx page designed? It accepts a query id as the parameter, which is the CustomerEntryLookup we specify. In the query designer, it is designed in this way.

The lookup. aspx page accepts input parameters. Its initial trial page is designed in this way.

 
 

  
  
protected void Page_Init(object sender, EventArgs e)  
  
  
{  
  
  
            LookupName = Request.QueryString["id"];  
  
  
           
  
  
            ILookupDialogManager _lookupDialogManager = ClientProxyFactory.CreateProxyInstance<ILookupDialogManager>();  
  
  
            string companycode = "TS";  
  
  
            DataTable table = _lookupDialogManager.GetLookupDialogData(LookupName, null, null, 0, 0, companycode);  
  
  
            Grid1.RecordCount = table.Rows.Count;  
  
  
 
  
  
              BindGrid();  
  
  
             
  
  
} 
 
 

Query by PAGE based on the total number of records. The code here is the paging code of the Grid. It is not complicated to see the definition of the BindGrid method.

 
 

  
  
private void BindGrid()  
  
  
{  
  
  
            DataSet ds = LoadData(Grid1.PageIndex+1);  
  
  
 
  
  
            while (Grid1.Columns.Count > 0)  
  
  
                Grid1.Columns.RemoveAt(0);  
  
  
 
  
  
            foreach (DataColumn colu in ds.Tables[0].Columns)  
  
  
            {  
  
  
                ExtAspNet.BoundField field = new ExtAspNet.BoundField();  
  
  
                field.ColumnID = colu.ColumnName;  
  
  
                field.DataField = colu.ColumnName;  
  
  
                field.HeaderText = GetTranslation(colu.ColumnName);  
  
  
                Grid1.Columns.Add(field);  
  
  
            }  
  
  
 
  
  
            Grid1.PageSize = PageSize;  
  
  
            
  
  
            Grid1.DataSource = ds.Tables[0];  
  
  
            Grid1.DataBind();  
  
  
 } 
 
 

It first deletes the original columns in the grid, generates new columns Based on the results, and applies multilingual translation to the column names. Pay attention to the Creation Time of the dynamic control. You should select it in Page_Init instead of Page_Load. When debugging, the page code is displayed as database pages, and only the set number of lines is returned each time.

The Grid paging event sample code is as follows, which is exactly the same as that of the GridView.

 
 

  
  
protected void Grid1_PageIndexChange(object sender, ExtAspNet.GridPageEventArgs e)  
  
  
{  
  
  
         Grid1.PageIndex = e.NewPageIndex;  
  
  
         BindGrid();  
  
  
} 
 
 

Next let's take a look at the code of the two button methods on the lookup. aspx page. The simplest is to Close the form directly without returning any value to the main form. Its code is the easiest, as shown below:

 
 

  
  
btnClose.OnClientClick = ActiveWindow.GetHideReference(); 
 
 

The Code is as follows:

 
 

  
  
protected void btnSaveClose_Click(object sender, EventArgs e)  
  
  
{  
  
  
            int rowIndex = Grid1.SelectedRowIndex;  
  
  
            GridRow row = Grid1.Rows[rowIndex];  
  
  
 
  
  
            ILookupDialogManager lookupManager=ClientProxyFactory.CreateProxyInstance<ILookupDialogManager>();  
  
  
            LookupDialogEntity lookup = lookupManager.GetLookupDialog(LookupName);  
  
  
            List<string> keyFields = new List<string>();  
  
  
        
  
  
            keyFields.Add(lookup.KeyField1);  
  
  
            keyFields.Add(lookup.KeyField2);  
  
  
            keyFields.Add(lookup.KeyField3);  
  
  
 
  
  
            List<string> values = new List<string>();  
  
  
            foreach (string keyField in keyFields)  
  
  
            {  
  
  
                string value = string.Empty;  
  
  
                if (!string.IsNullOrWhiteSpace(keyField))  
  
  
                {  
  
  
                    ExtAspNet.BoundField field = (ExtAspNet.BoundField)Grid1.FindColumn(keyField);  
  
  
                    string f1 = field.DataField;  
  
  
                    object f2 = Grid1.Rows[rowIndex].States[field.ColumnIndex];  
  
  
                    value = Convert.ToString(((DataRowView)(Grid1.Rows[rowIndex].DataItem))[keyField]);                
  
  
                }  
  
  
                values.Add(value);  
  
  
            }  
  
  
            PageContext.RegisterStartupScript(ActiveWindow.GetWriteBackValueReference(values[0], values[1], values[2]) + ActiveWindow.GetHidePostBackReference());  
  
  
 } 
 
 

This part of the Code has two intentions: Take the value in the Grid and return it to the main form. Because you need to refresh the main form, add GetHidePostBackReference () to make the main form send back, the windowdid close, designed at the beginning of the article, ReloadEntity completes the re-binding of objects.

The principle of query and lookup is the same. They are all used for custom data searches. Query is used for relatively independent functions and is executable. lookup is used for searching and Returning Field Values to facilitate data input in the form. In the query designer, you can enter SQL statements or call stored procedures not only for Object Design queries.

This makes it easy for you to expand the system query function without secondary development.

Link: http://www.cnblogs.com/JamesLi2015/archive/2012/09/25/2700992.html