Watch the video below – Working With Text Fields – for additional information about using Text fields in Ninox.

Text fields are used in Ninox to store and present numeric, alphabetic and special characters. The contents of a text field can be directly modified, assuming adequate security rights and privileges, by end users without those users having to interact with, or effect, the underlying database calculations or data model.

Text fields are best used to store small amounts of content such as a name or address.

For longer alphanumeric text strings, consider using Multi-Line Text or Rich Text fields.

The Text field parameters and configuration options screen is displayed in the image below with each options use described in the text below the image.

FIELD NAME – The field name is the unique alphanumeric string that identifies the field in terms of what the contents of that field represents. No two fields in the same table may have the exact same name

REQUIRED – Ninox users have the option to define whether or not the field may be empty. If the “Required” field is set to “Yes”, no record may be stored into the data table if the value of the field is null.

DEFAULT VALUE – This is the value that Ninox will insert into the field immediately upon a new record’s creation within the table. The default value may be overridden/edited by the end user assuming adequate user rights and privileges. Users will often assign a default value to a field that has been defined as Required so as to ensure efficient data entry processes. HOWEVER, if the field is a compliance where, as the database administrator, you with to force the user to recognize the importance of the field and its contents, set Required to “Yes” and leave the Default Value blank. This will prevent a record from being entered into the table until the user has completed content entry into the field. A required field that is null will glow red until such time that content is provided.

TOOLTIP – Often referred to as “hover help”, this is content that will appear in a small balloon at the point where the cursor is when that cursor is left to hover over the field for a few seconds. Tooltips are used to assist the user in understanding what is expected to be entered into the field. For example, a First Name field in the Employee table of a Human Resource database application may include a tooltip that says “Please enter full legal name as it appears on the employee’s driver’s license”

DISPLAY FIELD ONLY IF – This field accesses the Ninox formula editor where the user may define the condition under which this field, and its contents and name, remain visible in the form view of records in this table. A field will only remain visible if the DISPLAY FIELD ONLY IF is left blank or if the formula that appears in the field distills down to a “True” state. For example, to ensure that a field remain invisible at all times and in all situations, a user may enter the formula 1=2 or null. In either of these cases, the result of the formula will always be false and, as a result, the field will never be displayed. Conversely, if you wish for a field to appear or disappear based on the evaluation of a condition, you may define that condition here. For example, if an employee indicates that s/he will be parking a car at the worksite, you may wish for a field to appear where the system can collect that license plate number of that vehicle. In this example, there may be a field named “Make of Vehicle” and another field named “License Plate Number”. The DISPLAY ONLY IF formula determining whether or not the License Plate Number field appears would be ‘Make of Vehicle’ != null. This formula distills down to “only present the License Plate Number field for entry when the Make of Vehicle field is not blank. At such time that no personal vehicle is specified, there will remain no need to collect the license plate information.

TRIGGER AFTER UPDATEPlease see Working With Triggers in the Ninox Programming Language section of this users manual.

WRITEABLE IF – This field accesses the Ninox formula editor where the user may define the condition under which the contents of this field may be entered or, if they exist, may be edited. Any formula entered into this field must evaluate to “True” for the contents of this field to be modifiable by the end user. If this field is not blank and the formula entered into the field evaluates to a false state, the field will be locked and its contents unmodifiable. For additional information, please see Table Writes in the User Rights, Security & Passwords section of this users manual.

GLOBAL SEARCH – A user has the option to indicate whether or not each specific field within a table is to be targeted by the Ninox Search Engine. If Global Search is selected, the contents of this field will be searched when the Ninox Search Engine (Find) mode is activated. If deselected, the contents of the field will be ignored during search operations. Note that, by default, if the table is excluded from search operations by virtue of its configuration all fields in the table will be ignored irrespective of this setting. Please see Search Engine for additional information on the Ninox Find feature and table configuration.

[DELETE FIELD] – The red button that appears in the bottom, left-hand corner of the screen, if clicked, will give you the option to delete this field from the table. If you confirm the wish to delete the field, the field, and all content in this field in all records of the table will be eliminated. The Delete Field operation can not be undone, so make sure you have made a backup or archive of your Ninox database application prior to deleting any fields.

Revision: 8
Last modified: 2019/03/12


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Please do not use this for support questions.
For customer support, please contact us here.

Post Comment