Name Map is like the caption of Access which allows the display custom text instead of the field name in tthe Grid column header. Optionally, you can supply the calculated expression required for sort, edit and filter criteria. The TextHolder - GH1 tag enables user to supply a fully customized header. Therefore the namemap feature in Tornado is effective mostly in assigning a formula to the calculated field. GH1 is a text anchor that you can place at the header location. (See dbTextHolder).

• Obj.dbNameMap="(;,)field=GridFieldNameNumber | Alias=MapName | Tag=Tag | Formula=CalcExp, ...repeat"
• Obj.dbFormNameMap="(;,)field=FormFieldNameNumber | Alias=MapName | Tag=HeaderTags | Formula=CalcExp, ...repeat"
  Note: FormNameMap if combined with a Grid, the only thing it can change is HeaderTag and Alias
• Obj.dbEmbeddedGridNameMap="(;,)field=GridFieldNameNumber | Alias=MapName | Tag=HeaderTags | Formula=CalcExp, ...repeat"

 

Keyword	Description
Fied	Field name or number of Grid or Form to be mapped. Field=CustomerID , Field=0
Alias	The mapped name. Alias=My<br> Name
Tag	Class=?? COLSPAN=?? Align=??. Due to the new structure of being able to replace the entire header with GH1 and header=false. Tag use is not effective here. Selecting a new class will change the appearance of the cell.
CalcExp	This optional parameter defines the calculated expression of the field. This parameter is required for sort, filtering and editing criteria. See following case study examples. Note that the formula field must provide the appropriate wrappers for the alias fields [MS] (ORACLE) etc..

 

 

Simple Example in changing just the header names