Why link Textbases?
The main reason that you link textbases together is to avoid having to replicate information that is common to many records or to more than one textbase. By storing the common information in one textbase, you can reference it from other textbases.
Deciding which textbases to link is an important, but not difficult, decision. Typically, you use linking to model a many-to-one relationship between different types of records.
In the simplest case, a many-to-one relationship can be accomplished with multiple entries in a field. For example, many phone calls to a particular customer can be logged in a single field in the customer record. However, if you need to track ...view middle of the document...
The textbase that contains the Link field is called the ‘primary textbase’. The other textbase is called the ‘secondary textbase’.
Part of the decision about linking textbases is to determine which textbase should be the primary and which should be the secondary. You will be able to edit information in the primary textbase, so make the primary textbase the one that you will be working in most frequently. Which accessed from a primary textbase, the secondary textbase information is available for reference only. Therefore, the secondary textbase should be the one that contains relatively stable information. To change information in a secondary textbase, open it directly.
You may want to protect your textbases from unwanted access. For example, you do not want library users to be able to edit records in your online catalog. One way to protect textbases is to place them in a directory to which users have read-only rights. Another option is to use a Silent password to keep library users from seeing confidential information and from editing the textbase structure or records. You may also want to assign various passwords to library staff, for certain purposes.
There are three types of passwords: Master, Field Access and Silent. The master password protects the...