TXT
The TXT connector enables you to read and write comma-separated or fixed-length text files. It can be used to exchange data between Uniface and external tools such as spreadsheet applications.
| Connector Feature | Description |
|---|---|
| Mnemonic: | TXT |
| Supported Version: | For the most current information, see the Platform Availability Matrix. |
| Supported utilities | None |
| SQL | Not supported. |
| Stored procedures | Not supported. |
| Unicode | Supported |
Restrictions
Note: The TXT connector is not a normal DBMS connector, so database-related functionality is not supported.
For example, the TXT connector:
- Stores everything in a character string format.
- Does not update or delete existing records—it can only read them, and append new records.
- Does not manage fields. When you create a table at run time, the TXT connector creates a text file to which all of your records are sequentially added.
- Does not maintain keys or create indexes, and ignores the rules for primary and candidate keys. However, the default ProcScript in a store trigger attempts to validate a key, and detects occurrences that do not comply, so validation code may need to be deleted from the default ProcScript.
- Does not support the selectdb ProcScript statement or where clause. If either of these statements is used, the TXT connector ignores it.
- Does not support referential integrity or locking. You cannot use ProcScript statements that lock occurrences, such as read/lock and reload.
ICaution: t is strongly recommended that you do not use text files for Uniface system information because no locking is available at any time, and you cannot update or delete any records. In addition, text files should be used by single users only.
