Text field with a maximum length of 1,500,000 characters.  The Memo column of the logger window (5) shows the number of characters that contains the cell (---- if it is empty). When given focus with the mouse to a line of the log field, the window 4 (which normally contains the note of a item), goes to show the contents of the memo of the line. To remember this momentary change in its use, the signboard higher (6), which normally indicates Note, goes to state Memo. When it becomes to give focus to an item of the main windows (1) or links (2), again bring the contents of the Note [1].

Text field with a maximum length of 260 characters. Its use can be anything, but for certain special features of the logger, it is hoped to find here the direction (path) of an object, the address (URL) of a Web resource, or an e-mail address.

Text field with a maximum length of 40 characters. Like the previous field, its use can be anyone, but certain features, hope to find here the title of one of the commands defined in the catalog of commands.

As will be seen over these pages, the Zator dBase lets keeps some control over objects in the system (external files to the dBase). For example, .DOC files of MS Word, which can be called to edition from dBase, or .MP3 files that can be played following commands launched from a hypothetical catalog of songs in the Zator dBase. However, dBase can also accommodate these files internally; extract then to a temporary file when necessary, use them, and re-stock when finished.

This cell of each line of the log field may contain one of these binary files. As with Memo column, the cells in this column show the size (---- if it is empty) of the object (BLOB) in field [2].

	Figure 1

As can be inferred from the description above, the use of the log is at the discretion of the user, and can be adapted to a multitude of circumstances. The limit is the imagination and needs of each one.

Note that the type of content in the log of the atom A does not have to coincide with the use of the log in the atom B. As a sample, and only one stroke as the matter, suppose that certain atoms in a dBase contain data about patients of a doctor; each line could contain the result of a query, an exploration; a visit; a test, etc.  In addition to the endorsements of the case, the load cell could contain the digitization of a radiological test or any other content, but could also involve external files referenced from the field address.  Conversely, if other atoms correspond to data about students, the corresponding lines of their logs might contain the results of partial evaluations, and so on. Finally, if an atom refers to monitor our own diet, the logger lines may contain only the dates and weights of our evolution.

We have devoted a special section for the detailed explanation of its characteristics and maintenance (D.8)

The access to this part of the information of the current atom is obtained by pressing the button , which goes the window to display the extended fields, taking the aspect shown in Figure 2.  Pressing the button becomes the initial presentation (Fig. 1). Note that only have changed the upper space of the window, the one normally occupied by the main windows.

There are two types of extended fields:

They are labeled Name, Profession, Alias, Country, etc. Allow a line of text of variable length in each case (indicated in the process of creation).

Is the labeled eDir (e-mail addresses); its features are similar to those indicated above for the log, although in this case only has three columns: Number; Description and Executable.

Its purpose is obvious; store e-mail addresses, telephone, fax, etc. While in reality can be used to accommodate any type of data, for certain specific uses it is expected that the cell Executable contain the title of one of the commands defined in the Catalogue of commands. In these cases, the cell Number may contain an e-mail address, although it could be anything else.

Note: once changed, the titles are valid for all records of the dBase amended. If you need different types of labeling, the only recourse is to establish different dBases, and the ease to change the work area that offers the application.

§4  A final advice

Once we realized the potential of Zator, it is possible that, if you have any kind of information scattered; documents, pictures, music, literature, etc.  Think in introduce and manage through OrganiZATOR, which would not be surprising, because in the end, the application is designed for that. However, before embarking on a massive influx of data, our advice is to think carefully the schedule and apply preparatory testing in small-scale. Checking in each case the usability, performance, ease of search and locate information, and so on. The reason is that Zator is extremely flexible, and this flexibility could become a drawback until you have some mental training and some practice. For sure that after a while, you think up at least half a dozen possible ways to mount the information. While all may be equally valid, it may be a better or more appropriate than another for the purpose for which it is proposed and your particular way to use the data.

§5  Examples

As an example and a source of ideas, the dBase supplied with the application includes some atoms that may consider helping in the learning of their functioning. We advise not delete them until you are sure that you understand all corners of the dBase.