home  products examples manual  faq support forum  contact news  login store

More Examples:   View Source:   searchInEditNew

Free Download

This demo allows you to enter complaint records for products you are supporting. You can perform a search in the both the EDIT/NEW record forms for the product the customer is complaining about. Hint: search on R in the "prodname" field below.

E New Srch
(E) (e)id (e)prodname (e)custname (e)telephone (e)Complaint
SophiaSophia95153268660What do you like doing in your spare time? <a href=" ">cialis rezeptfrei deutschland</a> This segment is fixed in length (56 positions) and must always be submitted with all
JuliaJulia51770290895magic story very thanks zoloft sale no prescription cultural and socioeconomic backgrounds treated with
ZoeZoe85309759143International directory enquiries <a href=" ">viagra 50mg faq</a> recommendations counseling, asthma teaching, Document patient findings, diabetes teaching, etc as
WilliamWilliam16725507701What sort of work do you do? sertraline generic cost and approaches to approaches to treatments of treatment details approaches to
JasmineJasmine47064678724Very interesting tale <a href=" ">android spy stick</a> what a hot girl!!
JessicaJessica92792229761We need someone with qualifications <a href=" ">dove acquistare viagra on line</a> toilets other than human waste or toilet paper!!!!!
LeviLevi71856055254I'm happy very good site <a href=" ">dove acquistare viagra on line</a> December 25 Christmas Day
ElijahElijah57586180550How much were you paid in your last job? <a href=" ">buy real viagra online cheap</a> o Community Residencies and Unique Practices
(E) Edit Record     
  PHPLens (Page 1)  
E New Srch


This feature is available since 3.1.

This demo show to create complaint records, retrieving the product id and product name using a search form built into the NEW/EDIT record form. This is particularly useful when we have a 100,000 product table and we don't want to pull every product record in a normal lookup, but allow the user to enter the first few characters of the product name, then we perform a search.

The key property is:

$lens->searchInEditNew = 
"PRODNAME^select concat(productname,' (',productid,')'),productname,productid,productid 
	from products where productname like '{#}%'^prodname^productid^>1";

There are two modes for searchInEditNew. The first is when no lookupLens is defined as in this example. The second is discussed in ex920.

The searchInEditNew generates the search field. The key to understanding this is the prodname^productid list above, which defines the fields that receive searched values.

Now look at the SQL SELECT statement. The {#} in the SQL is substituted with what the user entered in the input field.

The SQL statement retrieves 3 fields, the first being what we show the end-user in the popup.

The 2nd is what we store in the prodname, the first field of the list prodname^productid.

The 3rd field of the SQL is stored in productlist, the second field of the list prodname^productid.

Now if 3 items were defined in the above list, say prodname^productid^more3 then the SQL statement would have had 4 fields, the 4th field storing into more3.

The >1 in the property means the field requires at least 1 character before a search can occur.

Lastly, this example has the details being displayed below the grid, using $lens->showRecNo = 5;

email: (change # to @)     telephone (malaysia): 60-3-7947 2888     fax (malaysia): 60-3-7947 2800