Inmagic® DB/TextWorks® Version 7.0
README File

Application.messageYesNoCancel(message)

Clicking the Yes button on the message dialog box returns 1, the No button returns 0, and the Cancel button returns -1.

The method to include an "Enter password:" box on the query or edit page has changed. Now you add a form or query box and specify whether it's a password box using the HTML tab on the Box Properties dialog box. This gives you more control over the appearance and position of the password box. Note that for edit forms, to enable the "Web box treatment:" droplist on the Box Properties>HTML tab, which is where you specify that the box is a Password box, you must first save the form as an Edit Window form.

Box background colors are now retained. If you use a background image, you may want to avoid using a box background color because box background colors are solid, not transparent.

When you use query/edit pages on the Web, the selected box is highlighted. To disable this feature, see the BoxHighlighting=0 option in the [WebPublisher] section of the INMAGIC.INI Entries section.

The HTML source now includes <label> tags around box labels.

Improved Formatting

Box Height

Tab Order

[Inmagic DB/TextWorks]
TabToHTMLBoolean=1

0 = Tab skips AND/OR/NOT droplists. The only way to change the state of the droplist is with the mouse.
1 = Tab behavior corresponds to the setting for 'Allow tabbing to Boolean query buttons' in Tools>Options>Search. (default)
2 = Tab goes to AND/OR/NOT droplists.

If you want to modify the setting, you must edit the INMAGIC.INI file when DB/TextWorks is not running before you use Export Query Screen to HTML. In actual practice, there normally will not be any reason to do so. Simply change the setting for 'Allow tabbing to Boolean query buttons' in Tools>Options>Search to the desired option before using Export Query Screen to HTML.

If a field has a validation list, Web edit forms automatically turn the box label into a hypertext link. When you click on the link, a Choices Browser window appears, which you can use to paste terms from the validation list into the edit box. If you don't want the validation list links to appear for all fields, see the AutoIncludeValidationLinks= option in the [WebPublisher] section of the INMAGIC.INI Entries section.

DB/TextWorks 7.0 permits you to specify default values for fields in new records created using Web edit forms. This feature is similar to the desktop Record Skeleton feature. To specify a default value, on the Box Properties>Contents tab, fill in the "If empty use:" box below the field list and either Add or Replace the field. The text in the "If empty use:" box will be used as the default value for that field in new records.

In previous versions, if an edit box had a minimum height of 0 or 1, the box was exported as an INPUT box. In version 7.0, it's exported as a 1-line-high TEXTAREA box. When you type multiple lines of text in the box, the box expands, but the boxes below do not move down. When you tab off the box, it reverts to its minimum height. This behavior happens regardless of whether you select CSS on export. To prevent this behavior, set the minimum and maximum height of the box to be the same (or Minimum=0 lines and Maximum=1 line). Remember that if the Minimum Height is larger than 0 lines, an empty box will appear when the field is hidden by the current password.

• The two main field lists in on the Edit Textbase Structure and Edit Fields dialog boxes.
• The field lists on the Textbase Passwords dialog box in Edit Textbase Structure.
• The Field list on the Query Choices Browser for query boxes which search multiple fields. You can still use the Query Screen Designer to control the order of fields, so the index for the first field in the list is the one that appears when you use Browse Choices. This applies to WebPublisher Word Wheels and choices droplists as well.
• The field lists on the Inmagic.net>Configure screens.

Application.currentMenuPath
Application.currentMenuName
Window.formName

Application.currentMenuPath is especially useful on Windows 2000 and XP systems where the current directory is not the "Start in" directory specified in the shortcut properties.

When you use Export Editing Form to HTML you will be asked whether you want to use cascading style sheets to retain formatting. If the textbase has passwords, you will also be asked whether you want to add an "Enter password:" box to the form.

• In previous versions, the new box was the width of the window. Now it will be the width of the box that was selected when you used Add Box.
• For a new query box, if you click OK when the box is empty, the selected field will automatically be added to the box. Previous versions displayed a message indicating you needed to add a field before pressing OK.

XML import using the default XSL style sheet will import either the 6.0 format or the 6.1 format.

The default XSL style sheet is no longer created automatically the first time you do an XML import. A new Save As button on the File Format tab of the Import Options dialog permits you to specify the file name and path. You can then modify this style sheet for later use.

To enable this option, you must first connect a thesaurus to the field. You can do so using either Maintain>Set Up Thesaurus outside Edit Textbase Structure, or by using the new buttons in the Thesaurus group on the Text Options tab.

To add terms to the list, you use the normal Maintain Thesaurus interface.

In effect, this means that you can share a validation list across fields or textbases. And since USE entries in a thesaurus behave like a substitution list, you can also in effect share a substitution list across fields or textbases.

This means that you can now browse a thesaurus from the Command Query window.

The Query and Editing Choices Browsers now have a new Search button that is enabled when Thesaurus is selected. When you press the Search button a new dialog comes up which allows you to search the thesaurus for words or phrases, just as on the old Browse Thesaurus dialog.

The Info button from the old Browse Thesaurus dialog is labeled Properties on the Query and Editing Choices Browsers.

First you must use Edit Textbase Structure to add a single new field with the new Access Control field type (at the bottom of the list of field types). Then add entries to the special validation list for that field, indicating the possible classes of records you might want to protect or make available. For example: "on order" or "confidential". Then use the Passwords button on the Edit Textbase Structure dialog to specify Record Level Security Settings for each field access password and/or the Silent password for each class of record.

When you import an XML file using the default style sheet, the default textbase .XSL file is created with the same name and in the same directory as the textbase. This file is deleted if you use Edit Textbase Structure to change the structure.

XML Import first converts the file to Inmagic Tagged Format. So any rejected records will appear in the exception file in Inmagic Tagged Format.

Important! Characters between ASCII 128 and 159 (hex 80 through 9F) are not supported for XML Import; they will be imported as question marks (?). This character range includes the trademark symbol (™), the m-dash, open/close quote characters, a couple of daggers, and other characters. See the Windows Character Map in the Accessories group for a complete listing.

When this option is on, every time someone opens the textbase, DB/TextWorks writes to a new file: the textbase .SLT file. This file has the same name and directory as the textbase with a .SLT extension. For example, a textbase named CATALOG would have a CATALOG.SLT file. The line in the file shows:

<the slot in use>: <the program used to open the textbase> <the machine name>:<the user name>

For example:

Slot 2: Inmagic DB/TextWorks LIBRARY:lisa

When the user closes the textbase, the line in the .SLT file is cleared.

You can open this file with any text editor (e.g., Windows Notepad) to see who has the textbase open at any given time. Note that if someone turns off or reboots their computer while the textbase is open, the line in the .SLT file cannot be cleared. However, when the last person or program exits a textbase, the entire file is cleared.

Sample textbase log file section using Details=3:

The record numbers in the locked/unlocked messages are the internal record numbers, not any number that appears in the textbase record.

5.1 - Cannot delete all entries from field '<name>' because it has Required validation [16948]
5.2 - Required field '<name>' cannot be empty [16500]

If any scripts used the old error number [16948] to detect this specific condition, you'll need to change the script to use the new error number [16500].

Now DB/TextWorks displays a message indicating the textbase is empty when you open the textbase, and any time you try to perform a search. To make the message go away, add at least one record to the textbase.

In version 5.1, when you paste a box into a form/screen which already has a box with the associated script name, the script name is incremented. For example, if you copy a script button whose script name is "button1", and paste it into the same form, the new button will have the script name "button2".

Field '<fieldname>' occurs more than once in the first row. Import stopped.
Unknown field name '<fieldname>' in the first row. Import stopped.

Notes:

- The term and word indexes for a single field counts as two indexes.

- Indexes cannot be rebuilt if there are any deferred updates.

The file attachments are retained the next time you open the dialog to make it easier to send the same attachment to multiple recipients. File attachment lists are textbase-specific (stored in the textbase IDI file).

Send Report as Mail now has a progress dialog with a Stop button when you select "Mail each record to a different address".

Also see the new Command.sendMailEx() script method below.

A new OmitCurrentRecord() method is available for Recordset scripts. It omits the record from the set and automatically does a MoveNext().

[Help]
HelpFileName=DBTLIB
Menu=Help on &DB/Text for Libraries

Query and menu screens exported with an earlier version of DB/TextWorks will continue to work with WebPublisher 5.0, and query and menu screens exported with DB/TextWorks 5.0 will also work with earlier versions of WebPublisher.

c:\dbtext\dbtext32.exe -m c:\data\mymenu
c:\dbtext\dbtext32.exe -m "c:\data\my-menu"
c:\dbtext\dbtext32.exe "c:\data-lib\catalog"

You can right+click on a red word to see a list of suggested corrections, or select Ignore All or Add. Add updates your private user dictionary (USERDIC.TLX). Note that the normal right+click menu (Cut, Copy, Paste, etc.) is not available for words which are red.

The following new script commands are now available:

scanImage()
selectQueryScreen()
selectQueryScreenEx("name")
selectMenuScreen()
selectMenuScreenEx("name")
textbaseHelp()

For example, if you have three textbases: CAT99, CAT00 and CAT01, you could map both the Authors field in the CAT00 textbase and the Names field in the CAT01 textbase to the Author field in the CAT99 textbase. When the end-user types search criteria in the box containing the CAT99 Author field, WebPublisher will also search the Authors field in CAT00 and the Names field in CAT01. Then WebPublisher will display the report using the forms specified for each textbase. Note that records from each textbase are displayed separately; first the records for CAT99 using its form, then the records for CAT00 using its form, etc. WebPublisher uses the same mechanism to locate the search textbases as it does for the lead textbase: the information stored in DBTWPUB.INI. Therefore, all of the textbases (lead & search) must have unique names, even if they reside in different directories.

Note: You must be sure to save the query screen in the Textbase File (Public) and not to rename or delete it after exporting it to HTML. WebPublisher reads the query screen in the lead textbase to determine the names of the search textbases, the field name mappings, and which forms to use.

Setup Workstation now sets a registry key which DB/TextWorks checks on startup to verify that Setup Workstation has been run on this machine. If the registry key is not set properly, DB/TextWorks displays a message indicating you need to run Setup Workstation then exits.

IMPORTANT! This issue also affects the Run-time Version. See Important Compatibility Information: Run-time Version

You can connect a thesaurus to any Text or Code field. You can have different thesauri for different fields, or connect the same thesaurus to multiple fields, in the same or different textbases

The thesaurus is not a substitute for a validation list. It is meant to assist the cataloger but it doesn't enforce the use of a particular set of terms.

- Detect URLs, EMail links, etc. and convert to hypertext links

When this box is checked (as it is by default), items like the following in boxes in the Report, Display, Query, or Menu Screen window will automatically be converted to hypertext links:

- URLs (www.inmagic.com or http://support.inmagic.com)
- EMail links (mailto:inmagic@inmagic.com)
- File links (file://c:\data\library.doc or \\server\volume\directory\filename.ext)

When you click on the link, the system will launch the appropriate application for that type of link (Web browser, email program, word processor, etc.). The link does not have to be in an entry or box by itself, it can be part of a sentence or paragraph. EMail links must begin with "mailto:" in order to be recognized -- there's no need to change the records; simply add the "mailto:" as Beginning Text in the form.

Note: This option is ignored in the Edit window.

This feature is significant because the limitations inherent in some e-mail programs affect the Send Report as Mail option. MAPI launches your default email program and so is dependent on the functionality included with that email program. Several popular email programs do not include full MAPI functionality, and thus cannot support the "Mail each record to a different address" option for Send Report as Mail. SMTP connects directly to your mail server, and is thus independent of any limitations in your default email program.

function onFormOpen()
{
  Command.fitWindowToForm();
}

onFocus() - when focus enters the box (e.g., you click on it with the mouse)
onBlur() - when focus leaves the box (e.g., you press Tab)
onRecordSaved() - when the record has been sucessfully saved

These new triggers can be combined with the new script menu commands to implement some simple but useful scripts. For example, you might use onRecordSaved() to automatically move to the next record when you save the one you're working on:

function_onRecordSaved()
{
  Command.nextRecord();
}

The workaround has the occasional side-effect of permitting line breaks in unwanted places, such as between the elements of a URL, or if you are numbering field entries in a paragraph in a report, between the number and its entry. If this side effect is unacceptable, you can use a text editor to edit INMAGIC.INI on each workstation and change this line to V4Repair=0. If you experience Windows application errors after doing so the next time you use DB/TextWorks (e.g., when displaying a report), you must change back to V4Repair=1 or upgrade your Windows operating system to a newer or non-OEM version.

• Add pictures to forms, query screens and menu screens. The pictures can be either fixed images (e.g., company logos) or specified in Image fields in a record.
• Add Script Buttons to forms, query screens and menu screens. Script Buttons permit you to run a JavaScript or Visual Basic script.
• Specify form and box background colors, including custom colors.
• Cut, copy and paste a single box or group of boxes. For example, you can cut boxes from the Record Area and paste them into the Margin Area, or cut them from one form and paste them into another.
• Align boxes (Left, Right, Center)
• Justify Text toolbar buttons

• The various box-specific HTML options (Inline Image, Image Links, Treat as HTML, "See Also" links, etc.) all now apply to individual content items rather than to the box as a whole. They have also all been moved to the HTML tab of the Box Properties dialog.
• he Inline Image HTML Option now shows all image entries in the field. Previous versions showed only the image for the first entry. To show only the first image, use a picture box instead of an Inline Image.
• The Paragraphs tab of the Box Properties dialog gives you the option not to include a space between content items in a paragraph. Previous versions always automatically added a space between content items.
• Additional item numbering options ("i, ii, iii" or "A, B, C" or "a, b, c"). Previous versions offered only Arabic (1, 2, 3) or capitalized Roman numerals (I, II, III).
• Dashed lines indicate page dimensions regardless of whether the margin area is visible.
• When designing label forms, a black line indicates the outer dimensions of the label. When designing a new multi-label set (e.g., a book label set), inner lines indicate the dimensions of each label in the set; these inner lines do not appear after you save and reopen the label form.
• Demco & Highsmith labels have been added to the Stock Numbers list when designing a new label form

• The ability to center or right justify text within a box.

• Cascading menu screens. You can now add Menu Screen Boxes to a menu screen; you specify the name of a .TBM file. When you click on the menu screen box, DB/TextWorks opens that menu screen in another window.
• The ability to specify a "Screen Title" on the Screen Preferences dialog. The specified text appears on the title bar for the Menu Screen window and on the Window menu.

You can apply any box and background colors you select to existing saved forms, etc. without modifying them in the designers (default option).

If you select "Mail each record to a different address", DB/TextWorks will automatically email each record to the address(es) shown in the specified field in the record, without further interaction from you. Important: When using this option, each email addresses must be in a separate entry. You cannot, for example, type multiple email addresses in the same entry separated by commas or semicolons.

Note: the "Mail each record to a different address" option may not work with all email programs.

Note: This feature will not repair damage to the .TBA file or .TBU file (user file) where forms, query screens, etc. are stored. You must perform the steps manually if these files are damaged and, when you create the new textbase, uncheck the options which copy public elements and the user file.

Note that you can only copy text from within a single box. If you need to copy information from multiple boxes/records, you must still use Copy Special>Report or Copy Special>Record.

• Text pasted into the Edit window uses Plain Text format (i.e., does not retain any font information in the copied text).
• If the copied text includes search terms highlighted using Reverse Video, the font color is white. So it will look like the highlighted information is not there. You can use Tools>Options to set Display Highlighting to None or to a Color before copying text which contains highlighted search items. Or, your other application may have a Paste Special option which permits you to specify that the information should be pasted as "Unformatted Text".
• Copy Special>Report and Copy Special>Record still copy information in Plain Text format.

[defaults]
sLongDate=Mmmm d, yyyy
sShortDate=dd/mm/yyyy
iDate=1
indexDateFmt=dd-mm-yyyy

sLongDate= and sShortDate= control the formatting of dates in reports and the format of pasted, computed and automatic dates. They use the syntax shown on the Regional Settings dialog.

iDate= controls how dates are interpreted for indexing and searching purposes. iDate= must be set to one of the following values.

indexDateFmt= controls the format of date indexes shown in the Query Choices Browser and the behavior of Edit>Insert>Current Date (F4) in the Query window. Previous versions always used YYYY-Mmm-DD format (e.g., 1997-May-05). The following example will yield full month names (1999-January-01):

[defaults]
indexDateFmt=YYYY-MMMM-dd

The same setting controls the format of dates inserted using Edit>Insert>Current Date (F4) in the Query window. So be wary of using formats which use significant characters. For example, if you specify MM/DD/YY format, since a slash (/) represents a Boolean OR, you'll need to implement the SpacedRelOps=1 feature described later in this document.

Notes:

• sLongDate=, sShortDate= and iDate= are used in place of the Windows Regional Settings for a particular workstation. They are primarily useful for applications like DB/Text PowerPack and DB/Text WebPublisher, which do not use the Regional Settings unless specifically set up to log on as a user with the desired settings.
• The order of the date components (month, day, year) must be the same for sShortDate= and iDate=. If the order differs, there will be problems with indexing, searching and date calculations.
• If you use a numeric month for indexDateFmt=, the month/day order should match the order for iDate=.

You can rearrange and remove buttons without using Customize Toolbar. Press Shift and use the mouse to drag the button to its new location. To remove a button, drag it off the toolbar.

You can change the location of the toolbar from the top edge of the window to any of the other three edges. You can also "undock" the toolbar so that it's a floating toolbox. When the toolbar is undocked, you can use the mouse to resize it so that the buttons appear on several lines. Toolbar location for each window is stored in the Windows registry.

- the status bar
- the toolbar for each window

To hide/display the toolbar for a particular window, select that window, then use the View menu. To hide/display the Main toolbar, you must close all other windows.

Several menu choices have also been moved to the View menu. For example: Hide Boundaries, which used to be on the Tools menu, has been renamed Boundaries and moved to the View menu.

Ctrl+S will now save the contents of the current window. For example, if the Edit Record window is the active window, Ctrl+S will save the record. If the Form Designer window has focus, Ctrl+S will save the form.

Previous versions separated entries with a dashed line. The corresponding Form Designer feature, Tools>Text Formatting>Added Text>Entry Separator>Line is no longer available.

Print no longer uses the Orientation specified in the form. You must use Print Setup to select the correct orientation before printing.

User Preferences has been renamed to Options.

Refresh Record has been renamed Refresh and moved from the Records menu to the Windows menu. This menu choice now affects other windows, including Textbase Information (e.g., to reflect new record/user counts).

The Attributes menu has been removed from the Image Annotation editor. All of the options which used to be on this menu have been moved into the dialog brought up by the Annotation Properties choice on the Annotations menu.

Several menu options have been combined into pull-right menus. For example:

• Copy Record to Clipboard and Copy Report to Clipboard are now pull-right choices under Copy Special.
• Edit Validation Lists and Edit Substitution Lists are now pull-right choices under Edit Lists.

The two Copy Special choices on the version 3.0 Tools menu have been moved to the Copy Special pull-right menu on the Edit menu. Their default names are now "Application (1)" and "Application (2)". You can override the default names by using the Menu= option in the textbase INI file (see Additional Copy Special Button for more information).

In the Form Designer, Report Options>Record Spacing has been moved onto the General tab of the Form Properties dialog. See the "Distance between records" control.

The Textbase-Specific Help option now always appears on the Help menu. It is disabled if there is no textbase-specific help for this textbase. Previous versions permitted you to specify whether this menu choice appeared with an installation option in Setup - Configure.

All of the choices on the Attributes menu in the Image Annotation editor have been combined into a single dialog called Annotation Properties on the Annotation menu. The Attributes menu has been removed.

The User File Path dialog now has a Browse button to make selecting a directory easier. This dialog normally only appears the first time you run DB/TextWorks.

The Customize Toolbars menu option has been broken into two menu choices. A pull-right menu permits you to select whether you want to customize the Main toolbar or the toolbar for the current window. Previous versions displayed an intermediate dialog where you selected which toolbar you wanted to customize.

If a textbase chosen from the recent files list on the File menu causes an error, you are asked if you want to remove the textbase from the recent files list.

If your Windows File Options are set to "Hide file extensions for known file types", the .TBA extension does not appear. Otherwise, it does. For previous versions, the .TBA extension never appeared in the recent files listing.

If the textbase path matches the current default directory, the recent files list does not show the textbase path.

The "within Border" options for box Label Position. Forms created with earlier versions will use the equivalent label position which is not within the border. For example, "Center within Border" will become just Center.

The Line option for Entry Separators on the Added Text tab of the Text Formatting dialog.

Show Paragraph Marks on the Form Preferences dialog.

Previous versions permitted you to specify your own keyboard shortcuts (Quick Keys), status bar text or button text (ToolTip text) for menu choices -- this functionality is no longer available. You can also no longer specify toolbar icons, but all of the available toolbar buttons now have icons.

If no text is selected, Spell Check starts from the beginning of the current box and goes down, checking each box in tab order. The Spell Check Setup choice permits you to specify which fields are checked and which are skipped. By default, only Text fields are checked for spelling.

If text is selected, Spell Check checks the selected text regardless of whether the field appears in the list of fields to check in Spell Check Setup.

The Check Spelling dialog has an Options button for setting options such as whether to ignore capitalized words, etc. Spell Check ignores boxes which are read-only (e.g., password-protected).

Each user has their own Window settings for each textbase. They are stored in the [Window Placements] section of the <textbase>.IDI file in the user file directory. Window settings for windows which are not textbase-specific are stored in the [Window Placements] section of the INMAGIC.INI file.

You can use the new "Fit Window to Form" toolbar button and Windows menu choice to quickly resize the window after switching forms.

Exception: The Export Options settings on the 'Records to Export' panel not saved. Records to Export defaults to the current set; if there is no set, you must export the entire textbase. This option behaved the same in earlier versions. Use Current Sort is not retained because there often is no current sort, and you cannot sort when you choose Export Entire Textbase.

The Image Drive control on the User Preferences now permits you to type multiple drive letters (up to 12, no colon, no spaces). DB/TextWorks will search each specified drive, in order, for the image.

You can also specify an optional volume ID field for each textbase. The actual volume ID used can be different for each record. Edit the textbase INI file to include the following section:

[Images]
VolumeID=fieldname

Then for each record, put a single volume ID entry in that field.

If you use one or both of these features, DB/TextWorks will search in multiple places for an image before displaying a message that it cannot be found:

• on each drive specified, and then
• on each drive specified, with the volume ID field from the record preceding the image path

Sort=1

Notes: You must display the report for the sort to occur. This change only applies when Copy Special copies information from multiple records in the Report window (MultipleRecs=1 in the <textbase>.INI file).

You can specify menu text in the <textbase>.INI file. Specify an optional accelerator key by preceding it with an ampersand (&). If no menu text is specified, these choices default to "Copy Special (1)" and "Copy Special (2)". Example:

[SpecialVendor]
Vendor=launch
Menu=Pass to &Launch
SpecialField=Document
MultipleRecs=0

[SpecialVendor2]
Vendor=Invzn
SpecialField=Image
Sort=1
Menu=Pass to &Invzn

Dates in NNNN-NN-NN format are now always interpreted as YYYY-MM-DD regardless of your Windows Regional Settings (e.g., even if your short date format is DD/MM/YY).

The menu screen options which used to appear on the Special menu have been moved to a new menu called Menu Screens.

Diagnostic Support on the Special menu, which used to bring up a dialog combining the Check Textbase and Enable/Upgrade Network operations has been renamed to Enable or Upgrade Network.

This limit has been removed. Now, you can save menu screens with more boxes, forms with more fixed text (generally for use with WebPublisher), etc. Note, however, that you cannot use menus, etc. which exceed 64K with versions of DB/TextWorks, DB/SearchWorks, or WebPublisher before 3.0.

• a URL link (adds the HTML code to create an HREF link; field must contain one or more http, ftp, or mailto links)
• an email link (adds the HTML code to create "mailto" links)
• a "see also" search link (adds the HTML code so clicking on the link searches the textbase for that entry)

This option must be set deliberately by editing INMAGIC.INI. By default, the behavior is the same as it has always been; spaces are not required around search operators.

With SpacedRelOps=1 you can search for dates or URLs using slashes and colons without enclosing the search string in parentheses. Examples:

6/12/97
http://www.inmagic.com/f_sup.htm

cat / dog / fish
1 : 25

These options have been renamed to "WebPublisher Reports" and "WebPublisher Only". In addition, Write to File in HTML will use the current Report window form, regardless of whether it was saved as a WebPublisher Report.

When you open the textbase, DB/TextWorks automatically extracts the highest value in this field (including case and punctuation). The first time you create a new record, DB/TextWorks automatically increments this value (by 1) and fills in the Automatic ID box. You can edit this value if you like. For each new record you create thereafter during a session, DB/TextWorks will increment the last value saved. So you could, for example, have one user creating new records with values in the format "LW-0001" an The Automatic ID field will be left blank unless the Edit form includes an editable box for the field.

If you apply Unique Entries Only validation to an Automatic ID field, DB/TextWorks will automatically increment the field contents if what you type already appears in the index for that field. This will work best if everyone is using Shared Immediate indexing. If duplicate Automatic IDs are created using Deferred indexing, the records will be rejected when you post the deferred updates.

For unique Automatic ID fields, if you are not sure what the highest ID is, you can type a value which already exists in the field. When you move off the field, DB/TextWorks will automatically increment the value to the next unused value. For example, if your textbase has two sequences of numbers starting with "BNR 0001" and "DBA 0001", when you create your first new record after opening the textbase, DB/TextWorks will automatically fill in a value one more than the current highest value in the field (e.g., "DBA 0983"). If you are entering records in the "BNR" sequence, you can change this to "BNR 0001", and DB/TextWorks will automatically change it to the next available value in the "BNR" sequence (assuming there's already a record containing "BNR 0001").

• If you choose Textbase Information while in the Edit Secondary Record window, you see the textbase information for the secondary textbase.
• When you choose Edit Secondary Record, if the cursor is in a box containing a field from a secondary textbase, DB/TextWorks attempts to place the cursor in a box for the same field in the secondary textbase edit form.

By default, if a secondary textbase has a Silent password, it is used. If not, you are automatically prompted for the secondary textbase password when you open the primary textbase. You can also set a User Preference so that, even if the secondary textbase has a Silent password, you are always prompted for the secondary textbase password when you open the primary textbase.

Following are some sample uses for this feature. In both cases, you'd set up a Silent password with minimal access to the textbase and an additional password for "authorized" users.

• Textbases containing sensitive information which some users should be able to view through a primary textbase
• Textbases where only authorized users should edit records, but those users want to be able to use the Edit Secondary Record feature

Plain Text for importing into text editors and mail programs

Rich Text Format for importing into word processors like Microsoft Word and WordPerfect

HTML for generating static intranet or Internet Web pages

In some cases, you may need to design special forms to take advantage of these features. See the online help for more information.

Notes:

• The "DisableWriteToFile=" option in INMAGIC.INI is now obsolete, and will be ignored. Whenever you print to a file using the Generic / Text Only printer driver, you will really be using that printer driver.
• "Write Report to File" replaces the version 1.3 "Write Report to HTML" menu choice.

Annotations can take several forms including: lines and arrows, freehand, "sticky notes," highlighting, rectangles, ellipses, plain text, and sound (.WAV files). Legal professionals can achieve redaction by using black highlighting or opaque rectangles to block out parts of the image.

Image annotations can be protected by passwords so that only authorized users may add or change them.

Deskew - straightens out a crooked image

Despeckle - general image cleanup (see Despeckle= in the "INMAGIC.INI Entries" section of this file). This option is disabled when Scale to Gray is checked.

This option can be changed during installation or by running the Setup program and choosing Configure. Or you may add or edit the following section in the DBTEXT.INI file in the DB/TextWorks installation directory:

[Dates]
CenturyYear0=1900

For example, if you specify 1940, "96" means "1996" but "35" means "2035".

To avoid retrieval problems, you must rebuild the field indexes for any date fields containing dates prior to the specified year.

Note: If you set CenturyYear0 to 1901 or greater, a search for >0 in a date field will retrieve records after the year 2000 (e.g., January 1, 2000 and up). Previously, this search retrieved records after the year 1900. To retrieve all records with contents in a date field, use =* rather than >0.

See also Import Document - Word Processing Files in the version 1.2 features.

Note: If you have customized any of your toolbars, this button will not necessarily appear on those toolbars. You can either reset the toolbar or explicitly add the new button.

To create a new textbase from a textbase structure backup file, choose New Textbase from the File menu, specify a new textbase name, and choose "Restore from Textbase Structure Backup File" on the Create Textbase Structure dialog.

When you use Load New Textbase to import the records into a new, empty textbase, the annotation list is automatically recreated from this section of the file.

• The Check Textbase report file now includes recommendations for procedures to correct the problems.
• DB/TextWorks automatically displays the report file in a window and scrolls to the bottom of the file so you can see the recommendations.

You can also use View Check Textbase Report File on the Special menu to display this file (or any plain text file).

For many of you, this means that the first time you run version 2.0, the window will not be maximized. Just maximize the window and exit. The window will be maximized the next time you start DB/TextWorks.

Duplicate Record

(formerly Copy Record) Renamed to prevent confusion with the new "Copy Record to Clipboard" and "Copy Report to Clipboard" features.

Load New Textbase

(formerly Reload Textbase) Renamed to convey the fact that you should generally use this feature when importing a dump file into a new, empty textbase. When restoring a damaged textbase, this new textbase is created by choosing New Textbase, specifying a file name, then choosing either "Copy an Existing Inmagic DB/TextWorks Structure" or "Restore from Textbase Structure Backup" from the Create Textbase Structure dialog.

The User Preferences dialog now includes several options which were previously only available by changing the INMAGIC.INI file. Some of the options which were there previously have been moved into new categories.

On the Text Formatting dialog in the Form Designer, the following options have all been moved into one section entitled "Added Text": Beginning Text, Ending Text, Ending Punctuation, Entry Separator.

When you save a menu screen or QBE screen after exporting it to HTML, these values are now saved as part of the menu screen or QBE screen. For QBE screens, the forms selected on the "Export QBE Screen to HTML dialog" are also saved as part of the QBE screen definition.

This option permits you to easily create tables from your information. The box labels act as column headings for the table. The box height for all "cells" is automatically set the same within the limitations you specify. Note that the box width is currently ignored when you use the form with DB/Text WebPublisher.

To open this window, choose Saved Queries from the Search menu. You can also specify that DB/TextWorks automatically open the Saved Queries window when you open the textbase. See the "Initial Action" section below.

None	Opens the window specified in INMAGIC.INI. When you specify an initial action of "None" in a the menu screen, unless you explicitly edit the INMAGIC.INI file, the initial window is set to the Query By Example window. See the InitialWindow= option under "INMAGIC.INI Entries".
Initial Window	Opens the specified window.
Saved Query	Performs the search specified in the saved query you choose.

*** REPORT INTERRUPTED ***

This feature may cause a slight performance degradation. If you don't have any multi-image TIFF files, and want to disable this functionality, see the MultiplePageImage= INMAGIC.INI option.

Note that if the report is sorted using an exploded sort, you may get multiple printouts of some images. To avoid this, respond No when asked whether to display the report, and use Display Record instead. Images will be printed in unsorted order.

IMAGE.001 (3)
IMAGE.001 3

This check box is disabled unless you have selected a Computed Date or Computed Number field in the picklist. The field must also be indexed to use this feature.

Also, see Calculations - FCOUNT. The combination of these two features permits you to set up a field to quickly find records for which a specific field is empty.

The "Version:" line indicates whether you are using the Win95/NT version.

If you have installed the DB/Text Import Filter product, "DB/Text Import Filter: Installed" appears on the About dialog. Otherwise, this line is left blank.

***Term index node 5, field 'SUBJ', key 53=<key>
key is not sorted in correct sequence. Index rebuild recommended.

[Help]
HelpFilePath=c:\helpfile
HelpFileName=library

For the HelpFileName= line, an extension of .HLP is assumed; do not type the .HLP extension. If the help file is located in the same directory as the textbase, the HelpFilePath= line may be omitted.

If you don't use this feature, any textbase-specific help file must be located in the same directory as the textbase and have the same name as the textbase. For example, for a textbase named CATALOG, the associated help file must be named CATALOG.HLP.

The About DB/TextWorks dialog indicates whether the DB/Text Import Filter files are installed.

Existing users may need to use the Win3xFileName=1 INMAGIC.INI option if their Image fields contain comments after the image file names. (The Win3xFileName= option is now available as "Support only short filenames for images" on the Imaging tab of the Tools>Options dialog.)