| |
Field Setup
After loading the database, the database objects (tables, views, custom views) will be shown in the left pane (the database pane). Click on any database object to go to the Field Setup Page for that object at any time.
Note: ASP XMLMaker does not support BLOB fields. If ASP XMLMaker finds any unsupported fields in a table, an [Unsupported Fields] tab will appear. You can click on the tab to view the list of fields that are not supported.
The Field Setup pages consists of two section. The upper section is a grid showing available options of all fields. The lower section contain two panels, the [Format] panel and the [XML Settings] panel for the selected field.
Custom field display order by drag-and-drop
You can change the field order defined in the database by simple drag-and-drop. Simply click the Field Name column to select the field, then drag it to where you want. ASP XMLMaker will generate ASP and display records according to this order.
The grid consists of the following sections:
General
Properties
| Field Name |
Field Name (read only) |
| Data Type |
Data Type (read only) |
| Size |
Maximum field length (read only) |
| Caption |
Caption to be displayed |
XML
When you output XML data, you can output the field values as element of each row or as attributes of each row, depending on the requirement of the client applications. By default, [As Element] is selected, but you can even have both if necessary. Since ASP XMLMaker supports formatted field value, you can put original value in attribute and formatted value in element if necessary.
Properties
| As Element |
Output field value as element of each row |
| As Attribute |
Output field value as attribute of each row |
Search
The generated ASP script support searching, you can pass the searching criteria by GET or POST. Select the fields you want to support searching. Quick Search searches multiple fields for a search criteria at a time, while Advanced Search allows you can specify criteria for specific fields.
Properties
| Quick Search |
Include the field for quick searching. Default is true for string fields only. |
| Advanced Search |
Include the field for quick searching. Default is true for all fields. |
Format Panel
You can select how to format the field value:
Properties:
| None |
No formatting |
| Currency |
Display in currency format (VBScript FormatCurrency function) |
| Date/Time |
Display in date format (ASP XMLMaker FormatDateTime function) |
| Number |
Display in number format (VBScript FormatNumber function) |
| Percent |
Display in percent format (VBScript FormatPercent function) |
| String |
Format the field value with specified VBScript string function or custom function |
| Max Length (List page) |
Truncate the field value at specified max. length and append "..." to the end.
Note: This setting only applied to memo fields in list page and must be larger than 0 to take effect. |
| Custom Function |
Enter your own function to format the field value.
Notes:
- Do not change the generated function name.
- Write your code in VBScript.
- Custom Function overrides the Format settings specified above.
|
XML Settings Panel
| Element |
Value type - "Original" or "Formatted". If "Original", the original field value retrieved from the database is used. If "Formatted", the value formatted by Format settings above is used.
CDATA - The field value is output as a CDATA section. CDATA sections provide a way to tell the parser that there is no markup in the characters contained by the CDATA section. This makes it much easier to create documents containing sections where markup characters might appear, but where no markup is intended. CDATA sections are commonly used for scripting language content and sample XML and HTML content.
When an XML parser encounters the initial <![CDATA[, it reports the content that follows as characters without attempting to interpret them as element or entity markup. Character references do not work within CDATA sections. When it encounters the concluding ]]>, the parser stops reporting and returns to normal parsing.
For example, you can include either of the following CDATA sections in an XML document without causing the parser to report an error.
<![CDATA[</this is malformed!</malformed</malformed & worse>]]>
or
<![CDATA[if (c<10)]]>
Note Content within CDATA sections must be within the range of characters permitted for XML content; control characters and compatibility characters cannot be escaped this way. In addition, the sequence ]]> cannot appear within a CDATA section because this sequence signals the end of the section. This means that CDATA sections cannot be nested. The sequence also appears in some scripts. Within scripts, it is usually possible to substitute ] ]> for ]]>.
|
| Attribute |
Value type - "Original" or "Formatted". If "Original", the original field value retrieved from the database is used. If "Formatted", the value formatted by Format settings above is used. |
| Null Values |
Specifies how to output the field if the field value is null.
Handling type
- Empty - for example, <fieldname></fieldname> (as element) or fieldname="" (as attribute)
- Omit - no element/attribute for the field is output
- Null Value - use a special value to represent null, for example, you can specify "NULL", then the output will be: <fieldname>NULL</fieldname> (as element) or fieldname="NULL" (as attribute)
- XML Schema (for Element only) - for example, <fieldname xsi:nil="true"></fieldname>
Null Value - text to represent null value (for use with "Null Value" handling type) |
|
