Database and record structure

A -  Database and record organization

B - Horizontal links: between databases, between records, between list entries

C -  Hierarchical links (es. thesaurus, mother/sons records, text/notecards)

fields can generate indexes which are exclusive to the generator field, entirely derived from it (i.e. automatically created and updated); cannot be directly edited. Any field data and term list contents (sort of look-up) can be "crossed" in output to replace text: string + abbreviation(s)

some fields generate indexes which are entirely derived (automatically created and updated), cannot be directly edited. Field data and list contents (sort of look-up) can be "crossed" in output to replace text: string + alternate.txt; journal field + any journal.lst

Term Lists can be regarded as autonomous (see dedicated section): their content can be imported from external text lists, updated from records, derived from different fields, directly edited. Field data and periodical title list can be crossed in output: e.g. secondary journal title (with up to three abbreviations) can replace text entered in records Journal field 

some fields generate lists which are not only derived (i.e. automatically created and updated from record contents), for they can have independent entries and synonyms and can be directly edited

D - Ready, predefined record structure: features of reference types

Structure belongs to each individual database.
Also Database templates are supplied for bibliographic research databases, library catalogs, mail lists, note taking databases, etc. and can be custom designed. fields are identified by name; fields are identified by name; any field has got properties such as : content type (text, number, name, date, call number, literature reference sources); features : repeatable (multiple), required, unique, validate new entry, ignore leading words in searching and sorting, linked to a term table (plus : only tables terms allowed, expand abbreviations if contained), indexed for faster search; fields come with predefined properties but user can change, add, port to other fields; field properties are automatically the same in all RTs (i.e. if subjects field is required, it will so through articles, thesis, computer programs etc.)

if a field is deleted from RT, or RT is changed to a non-matching type, existing field content is lost;
as fields are identified by name, when fields names are changed in RT, styles are affected and must be manually fixed; also searching and global replace must take into account new names 

e.g. '5' is either "data file" or "medium designator" or "map type" in 3 different workforms: Data file, Newspaper, Map; if RT "Newspaper" -whereby 5 is "medium designator"- gets changed to "Journal Short form" which lacks 5, then 5 stays there with its content but no name, just number and can be edited;
no numeric fields apart from RN for sorting; internal pub. date format, Call number for sorting; if fields names are changed in workforms, styles are affected and must be manually fixed, searching and global editing are not

En: yes, according to RT-reference types + other default preferences they are all automatically shared among different databases on the same computer, separately  for each PC user, see above "Files".
fields bear "step" displayed name; fields are identified by the position they hold in the Generic RT, fixed across all reference types; some fields (e.g. names, journal titles, pages, URL, keywords, figure, caption) have peculiarities (internal coding, indexing for fast search, output formatting, sort...) that cannot loose or lend to other fields; but the link between a term list and a field is customizable 

when a field is deleted from RT (or mismatched), existing content is put to the corresponding Generic RT field; no numeric fields apart from RN for sorting; if fields names are changed in RT, styles are automatically updated, searching and global editing are not affected 

E - Number of record types and input worksheets

F - Can modify the exisiting record types (apart from changing name) and create extra

G - Number of fields per record

H - Can create extra fields

I - Fields attributes can be changed; can be applied to other fields

the attribute 'field linked to a term list' is customizable insofar as a field can be included in only one list to be chosen, while a list can include more fields

but can always decide whether input in a given field is mandatory or not

J -  Multi-value fields allowed

K - Record number
  1   - system assigned
  2   - reserved, cannot be altered
  3   - user assigned
  4   - allows duplicate numbers
  5   - renumbering
  6   - is a sortable field
  7   - is a searchable field
  8   - can be displayed in printed output
  9   - reuse deleted numbers
  10   - can be alphanumeric

RW: system assigned and reserved; it is a  sortable and searchable field and it can be displayed in output