Home   What's New    Inmagic Software    Consulting Services    Web Publishing Products    WebPublisher Examples
For IT Professionals    Web Database Hosting    Training Workshops    Bar Code Services    About Crew-Noble    Site Index    Contact Us

Inmagic® DB/TextWorks® Version 7.0
README File


Contents


Important Compatibility Information

DB/TextWorks 5.2 and 6.0 used MSXML3 for XML Import. DB/TextWorks 6.1 uses MSXML4. Any machines that will use XML Import must have Setup Workstation run on them while logged in as Administrator.

Textbases which use the Record-Level Security version 5.2 feature are incompatible with earlier versions of all DB/Text products (DB/Text WebPublisher, DB/Text PowerPack, DB/Text ODBC Driver, DB/SearchWorks, etc.). Earlier versions will not be able to open the textbase. If you do not use this feature, there is no incompatibility with earlier versions. PowerPack Lite 5.2 (which replaces Update Manager) and DB/SearchWorks Run-time 5.2 are available either on the CD or on the Version 5.2 maintenance update download page.

Query screens which use the WebPublisher Multiple Textbase Query version 4.2 feature are incompatible with earlier versions of DB/TextWorks and DB/SearchWorks. Be sure to update all copies of these software programs, or name the query screens in such a way that users with older versions will know not to use them.

Changes in scripting in version 4.1 affected the behavior of certain DB/Text for Libraries version 1.0 scripts. DBTLBFIX.* files were installed with the version 4.1 maintenance update and CD with instructions for correcting these scripts. The primary symptom is messages including strings like "[Recordset is not open.]." If you have DB/Text for Libraries version 4.1, these scripts have already been corrected.

Version 4.x forms, query screens and menu screens are not compatible with earlier versions. Once you save a form, query screen or menu screen using version 4.x, you will not be able to use that form or screen with earlier versions. Forms and query screens saved using version 4.x will not appear in lists in version DB/TextWorks or WebPublisher version 3.x or earlier. (They'll "disappear" as far as the version 3.x programs are concerned.) Menu screens saved using version 4.x will display the message "File 'menuname.tbm' cannot be read by the software." Note: If you accidentally save a form or query screen with v4.x, you can use Manage Textbase Elements in v4.x to export the form to a .XPF file, then use Manage Textbase Elements in v3.x to import the file. (You'll get lots of "unrecognized" errors on the import; choose to continue.)

Import Filters

DB/TextWorks 7.0 can use IFilter technology to extract text from documents. IFilter technology is installed with Microsoft Index Server, which comes with Microsoft Windows 2000/XP operating systems. This technology is also supported on Windows NT 4.0 systems that have the Windows NT 4.0 Option Pack installed.

Microsoft and other vendors have created IFilters for their software products and make them available for download. For example, Adobe has an IFilter that lets you import its Portable Document Format (PDF) documents.

DB/TextWorks will only use the IFilters if:

To disable the DB/Text Import Filter so DB/TextWorks will use the IFilters instead, rename the DBTEXT.MLC file. Do not do this if any of the workstations which will be using Import Document to import non-text documents run Windows 95/98.

Windows 2000

Be sure you have Service Pack 3 installed on all Windows 2000 workstations running DB/TextWorks. A hotfix included with Service Pack 3 addresses an issue where Windows 2000 may return incorrect data when performing read operations across a network. If this information is then written back into a DB/TextWorks textbase, it may affect its stability. For more information about this issue and Windows 2000 please see http://support.microsoft.com/default.aspx?scid=kb;EN-US;q307982.

User accounts on Windows 2000 (and Windows XP) machines often do not have write access to files in the Windows directory. If this is the case, the INMAGIC.INI file will be stored in the user file directory. The location will be recorded in the following registry key:

HKEY_CURRENT_USER\Software\Inmagic\UserFilePath

Novell Netware

To avoid locking errors on Novell Netware networks, add NovellLock=1 to the [Advanced] section of DBTEXT.INI.

Internet Explorer

Internet Explorer 5.01 or later must be installed on the workstation for certain features to work properly. Internet Explorer does not have to be your default browser.

Version 5.01 or later is required for:

  • Inmagic.net
  • XML Import (it is not required for XML Export)
  • Thesaurus
  • the "Check Items on Loan" screen in DB/Text for Libraries 5.0 and later.
  • the "Lend Multiple Items", "Return Multiple Items" and "Check Items on Loan" screens in DB/Text for Libraries 4.1 or 4.2.
  • Version 5.5 or later is recommended for Inmagic.net.

    Run-time Version

    Starting with version 4.1, the software checks a registry entry on startup to verify that necessary DLLs have been installed on the workstation.

    a) The Run-time Master disks do not include all the necessary Microsoft files (the install would be too large to fit onto floppies). You must require that end-users have at least Internet Explorer 5.0 installed on their systems in order to use the Run-time version. If you put the Run-time version onto a CD instead of floppies, you can include an Internet Explorer Setup on your CD and tell end-users to run it as part of the install.

    b) If your end-users don't install from the Run-time Master disks (e.g., if you install the Run-time Version onto a CD and tell them to run it from the CD), you must include some mechanism for setting this registry entry.

    HKEY_LOCAL_MACHINE\Software\Inmagic\Inmagic DB/SearchWorks\swVersion

    swVersion is a DWORD Value set equal to 420 (decimal).


    Version 7.0

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information.

    Version 7.0 - New Features

    Mouse Scroll Wheel Support

    DB/TextWorks 7.0 supports mouse scroll wheels.

    Import Document uses IFilters

    DB/TextWorks 7.0 can be set up so that Import Document uses IFilters from Microsoft and other vendors to extract text from documents in a variety of formats (Word, Excel, PowerPoint, PDF, etc.). For more information, see the online help and Import Filters.

    Supported Image Formats

    This version will display certain types of images, e.g., "progressive" JPEG files, that would cause "Unsupported image format" messages in earlier versions.

    Scripting

    There's a new kind of Application message:

    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.

    Version 7.0 - WebPublisher Features

    Export Query Screen to HTML and Export Editing Form to HTML have changed pretty radically in this version, so be sure to read this section carefully.

    Web Edit Links

    The Form Designer has 3 new types of links on the Box Properties>HTML tab: Edit record link, New record link, and Delete record link. These options create the corresponding type of link when the form is used with WebPublisher PRO. New record link is also available in the Query Screen Designer.

    Alternate Text for URLs, EMail Addresses & Image Links

    In the Form, Query Screen and Menu Screen Designers, the Box Properties>HTML tab now permits you to specify alternate link text for URLs, EMail links, and Image links (Form Designer only).

    Export to HTML

    The following changes affect both Export Query Screen to HTML and Export Editing Form to HTML. Some will also affect Web edit forms:

    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.

    The tab key now heeds the tab order specified in the Form Designer or Query Screen Designer.

    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.

    Export Query Screen to HTML

    Improved Formatting
    You now have the option to retain retain more formatting (font face, box/label positions, etc.). When you use Export Query Screen to HTML, you are asked whether you want to use Cascading Style Sheets. Respond Yes to retain as much formatting as possible.
    Box Height
    Export Query Screen to HTML now uses the Minimum Height of the box (or 1 if the minimum height is 0). Previous versions used the Maximum Height (which defaulted to 5 lines).
    Tab Order
    If you have checked "Show Boolean operators" on Tools>Screen Properties>HTML, you can now specify whether the Tab key will skip the Boolean droplists when the HTML query screen is used on the Web. The INMAGIC.INI file has a new setting:

    [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.

    Export Editing Form to HTML

    Several of these features apply to Web edit forms as well. Export Editing Form to HTML now uses iwpp-edit.asp in the ASP subdirectory of the WebPublisher installation directory. WebPublisher PRO 7.0 and later install the file there automatically. Existing HTML edit forms exported for use with WebPublisher PRO 1.0 will continue to work with dbtwp-edit.asp and the new version of WebPublisher PRO.

    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.

    Version 7.0 - Removed Features

    Copy an Existing INMAGIC/DOS Structure

    When you use File>New Textbase, it is no longer possible to copy an existing INMAGIC/DOS textbase structure.

    Import DOS Report Formats (*.fmo)

    When you use Maintain>Manage Textbase Elements, it is no longer possible to import INMAGIC/DOS report format files (*.fmo).

    Version 6.1

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information.

    Version 6.1 - New Features

    Store Custom Colors

    Custom colors are now stored for later use. Whenever you use the Define Custom Colors button on the Color dialog box to specify a new form or box background color, that custom color is preserved. It will appear on the Color dialog box the next time you open it. The custom colors are written to the INMAGIC.INI file when you exit DB/TextWorks.

    Sort Field Lists Alphabetically

    A new "Sort textbase field lists alphabetically" option appears on the Display tab of the Tools>Options dialog box. When this option is checked, field lists on various dialog boxes (e.g., Box Properties in the Form Designer and Specify Sort Order) will appear in alphabetic order. If the field list includes secondary textbase fields, they will be mixed in with the primary textbase fields. This option does not affect:

    Large Toolbar Buttons

    A new "Large buttons on toolbars" option appears on the Display tab of the Tools>Options dialog box. When you check this box and click OK, you'll see a message explaining that the buttons will not be resized immediately. Buttons on any new windows will use the new size. The toolbar buttons on any open windows will be resized when you close and re-open the window. Buttons on the main toolbar will be resized when you exit and restart DB/TextWorks.

    Disable "The textbase is empty..." messages

    A new "Notify when opening empty textbase" option appears on the General tab of the Tools>Options dialog box. This option is checked by default. To prevent these messages from appearing, uncheck the option. Unless a menu screen option specifies an initial action of the Edit New Record window, the query screen will be displayed. (Of course, you won't be able to use the query screen to search for records, since the textbase is empty.)

    Scripting

    There are three new scripting properties:

    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.

    WebPublisher - Export Editing Form to HTML

    There's a new option on the Form Operations menu in the Form Designer: Export Editing Form to HTML. If the form is saved for use in the Edit window, you can use this option to export a Web form for use creating new records with WebPublisher PRO. You cannot currently edit existing records using this feature. A DBTWP-EDIT.ASP file is provided for use with this Web form; put it in the same directory as the Web form.

    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.

    Analyze Textbase

    A new Analyze Textbase option appears on the Manage Textbases menu. This option will create a text file displaying some information about the records in the textbase (maximum number of entries in each field, etc.).

    Version 6.1 - Feature Changes

    Query screen - Add Query Box

    When you add a box to a query screen outside the Query Screen Designer:

    XML Import/Export

    Export in XML format now uses the same format as WebPublisher PRO (and WebPublisher 6.1), with the <inm:...> tags, etc. It also includes null tags for empty fields.

    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.


    Version 6.0

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information.

    Version 6.0 - New Features

    Use Thesaurus as Validation List

    On the Edit Fields dialog in Edit Textbase Structure, the Content Validation group on the Validation tab has a new option:

    Use Thesaurus as Validation List

    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.

    Scripts - New Event

    The new onQueryExecuted() script event for Query screens permits you to trigger a script when the search operation is complete.

    Version 6.0 - Feature Changes

    Browse Thesaurus combined with Browse Choices

    The Browse Thesaurus (Shift+F3) choice has been removed from the Edit menu. Instead, you now use Browse Choices to view the thesaurus. Thesaurus appears as an option in the List Shows group at the bottom of the Query Choices Browser and Editing Choices Browser. (If a thesaurus is used as a validation list, Thesaurus is disabled on the Editing Choices Browser, and you select Validation List to see the Thesaurus entries.)

    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.

    Set Up Thesaurus Available in Edit Textbase Structure

    In previous versions, you used Maintain>Set Up Thesaurus to connect and disconnect a thesuarus. In version 6.0, you can also connect & disconnect a thesaurus in Edit Textbase Structure. See the Thesaurus group on the Text Options tab on the Edit fields dialog.

    Query/Editing Choices Browsers Retain Width Settings

    Since version 4.0, you have been able to change the width of the Query Choices Browser and Editing Choices Browser. In version 6.0, the width setting is retained the next time you open the dialog.

    Version 5.2

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information.

    Version 5.2 - New Features

    Record-Level Security

    Version 5.2 permits you to protect individual records using passwords. You can either hide them completely or prevent users from changing them.

    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.

    XML Import/Export

    You can now import or export records in XML format. For Import you can specify an XML Style Sheet (*.XSL) file or use the default style sheet.

    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.

    Who Has a Textbase Open?

    Version 5.2 includes a new textbase INI or DBTEXT.INI option which permits you to record who currently has a textbase open. This option is off by default.

    [Advanced]
    EnableSlotLog=1

    If you set it in the DBTEXT.INI file, it affects all textbases. If you set it in the textbase INI file, it affects only that textbase. This option will also affect WebPublisher, assuming it has full rights to the file, and PowerPack. If you set the option in the DBTEXT.INI file, the file must be located in the Windows directory for WebPublisher and in the PowerPack installation directory for PowerPack.

    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.

    Enhanced Logging

    Version 5.2 includes a new textbase INI option which permits you to record in the textbase log file who is opening textbases, editing records, and locking records. This option affects DB/Text PowerPack as well.

    [LogFile]
    Details=3

    0 - no enhanced logging
    1 - logs when user opens or closes the textbase
    2 - logs when user modifes records (and opens/closes textbase)
    3 - logs when user locks/unlocks record (and opens/closes textbase or modifies records)

    Sample textbase log file section using Details=3:

    12/7/2001 9:52:53 AM: Textbase opened using slot 2 - Inmagic DB/TextWorks: LIBRARY:lisa
    12/7/2001 9:53:04 AM: Record 7460 locked - Inmagic DB/TextWorks: LIBRARY:lisa
    ID: 7529
    12/7/2001 9:53:49 AM: Record modified (deferred) - Inmagic DB/TextWorks: LIBRARY:lisa
    ID: 7529
    12/7/2001 9:53:50 AM: Record 7460 unlocked - Inmagic DB/TextWorks: LIBRARY:lisa
    ID: 7529
    12/7/01 9:55:43 AM: Record 7460 locked - Inmagic DB/Text PowerPack: ITDEPT:SYSTEM
    ID: 7529
    12/7/01 9:55:44 AM: Update posted by DB/Text Updater
    ID: 7529
    12/7/01 9:55:44 AM: Record 7460 unlocked - Inmagic DB/Text PowerPack: ITDEPT:SYSTEM
    ID: 7529

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

    Version 5.2 - Feature Changes

    Improved Next Highlighted Term Behavior

    For long records, when you use Next Highlighted Term (or Previous Highlighted Term) DB/TextWorks now scrolls the Report window so you can see the highlighted term.

    Import - Inmagic Tagged Format Line Length Increased

    The maximum permissible line length for Inmagic Tagged Format has been increased to 65500 characters. The earlier limit was 1024 characters.

    Special Menu removed

    The Special menu has been eliminated. "Enable or Upgrade Network" has been moved to the Tools menu.

    Script Error Description/Number Changed

    If a script Update() command returns an error because a field with Field Entry Required validation was left blank, the Errors(0).Description and Errors(0).Number have changed. The Number is in square brackets after the message below:

    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].


    Version 5.1

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information.

    Version 5.1 - New Features

    Inmagic.NET - Catalog Web Pages

    You can now catalog Web pages in Inmagic.NET. Choose Configure from the Inmagic.NET menu to set up the field mappings. Then choose Catalog Web Pages from the Inmagic.NET menu and follow the on-screen instructions. You can make several text selections from a Web page and specify which field each should be entered into.

    Inmagic.NET - Search toolbar button

    The Inmagic.NET toolbars now have a Find button available so you can find text on the page. Edit>Find is also available for all HTML Application windows (Inmagic.NET and the choices on an Applications menu).

    Messages when Textbase is Empty

    When a textbase is empty (contains no records), DB/TextWorks opens the New Record window (rather than the Query window) so you can start adding records to the textbase. This caused confusion for new users and for users who were trying to set up Initial Elements using the Menu Screen Designer.

    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.

    Enlarge buttons for Calculation Formulas

    Enlarge buttons are now available for calculation formulas for Computed Number/Date fields in Edit Textbase Structure, and for form calculations in the Form Designer. When you press the button, a resizable text editor opens. When you OK your changes, they're copied back into the text control on the dialog.

    Form Scripts Available for Label Forms

    Form scripts (e.g., those with a trigger of onRecordOpen) can now affect printed reports. Therefore, the Tools>Form Script menu choice is now available for label forms. For example, the script library includes a script to break a routing list into two columns.

    Designers - Pasting Boxes Increments Script Name

    When you copy and paste boxes in the various designers, any associated script name is copied as well. In earlier versions, when you pasted the boxes, they would retain their script names, which could duplicate the script names used by other boxes in the form. This could cause an existing script to stop working, or behave unpredictably.

    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".


    Version 5.1 - Feature Changes

    Edit Textbase Structure>Edit Fields Dialog Redesigned

    The Edit Fields dialog in Edit Textbase Structure has been redesigned to be easier to use.

    Thesaurus Info Window Size Retained

    DB/TextWorks now retains the size of the Thesaurus Info window.

    Delimited ASCII Import Messages Display Problem Field Name

    The problem field name now appears in the following messages to aid you in correcting the first line of the Delimited ASCII import file:

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


    Version 5.0

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information.

    Version 5.0 - New Features

    Relevance Ranking

    A new "Relevance-Ranked Order" option on the Sort dialogs permits you to specify that the most relevant records should appear first in the report.

    Designers - Enlarge Button

    Several of the text controls on the designer dialog boxes now have an associated Enlarge... button. When you press the button, a resizable text editor opens. When you OK your changes, they're copied back into the text control on the dialog.

    Check Textbase - Rebuild Damaged Indexes

    The Check Textbase dialog now permits you to specify that DB/TextWorks should automatically Rebuild Damaged Indexes if it finds any. You specify the number of damaged indexes it should be permitted to rebuild.

    Notes:

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

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

    Send Report as Mail Features

    The Send Report as Mail dialogs now include the ability to add file attachments. Note that the "File attachments" section is disabled for MAPI when "Mail each record to a different address" is not checked because you use your email client's New Message window to specify attachments in this situation.

    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.

    Scripts - New Functions

    The new Command.sendMailEx() method and Command.SendMailDescriptor() object permit you to create a script which sends a report as mail without any further information from the user. You can also use script input boxes to prompt them for information you might want to include in the script (e.g., the Subject). See the online help for more information and an example.

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

    Form Designer - HTML Options

    A new Advanced Options button on the Tools>Form Properties dialog permits you to specify information to be included in the <HEAD> section of HTML reports for WebPublisher, Send Report as Mail, and Write Report to File. This information appears after the information added by the DB/Text software (e.g., the page title).

    Textbase-Specific Help - Specify Menu Text

    You can now specify the text which appears on the Help menu for textbase-specific help files. The following example replaces "Textbase-Specific Help" with "Help on DB/Text for Libraries" (the & precedes the underlined shortcut key):
    [Help]
    HelpFileName=DBTLIB
    Menu=Help on &DB/Text for Libraries
    

    Version 5.0 - Feature Changes

    Export Query/Menu Screen to HTML

    Query screens and menu screens exported to HTML no longer include the dbtw_body() script function. Instead, the <BODY> tag, including any background color or image is included as plain HTML.

    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.

    Improved Command Line Flag Parsing

    When you start DB/TextWorks, command line arguments can now use either "-m" or "/m". Note: If your textbase or menu screen name includes a hyphen, you must now enclose it in quotation marks. Examples:
    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"

    Version 4.2

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information.

    Version 4.2 - New Features

    Inmagic.NET

    Version 4.2 has a new Inmagic.NET menu. The menu choices permit you to buy books online from a variety of vendors, and to download the bibliographic data associated with those purchases.

    Check Spelling as you Type

    If you select the new "Check spelling as you type" option on Tools>Spell Check Setup dialog, misspelled words will appear in red as you type. As with other options on the Spell Check Setup dialog, this option is textbase-specific.

    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.

    Print Starting with a Specific Label

    When you print using a label form, DB/TextWorks now prompts you to select which label you'd like to start with. The default is the first label. A picture appears on the dialog as a visual aid to help you remember how labels are laid out on the page.

    Script Input Boxes

    All three designers now permit you to add a Script Input Box to a form or screen. Use a script input box when you need information from the end-user to include in the script. For example, the import file name for a Command.importDataEx() script.

    New Script Functionality

    You can now use a script to set the state of the Boolean AND/OR/NOT buttons on query screens. For example, you might write a script to reset all the buttons to AND when you use New Query.

    The following new script commands are now available:

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


    Version 4.2 - Feature Changes

    Check Spelling Dialog

    Spell Check now highlights the misspelled word in the Edit Record window, rather than displaying the field contents in the Check Spelling dialog. This increases accessibility because you can use a larger font for your Edit Record window form if desired. The Check Spelling dialog moves around so that it doesn't obscure the highlighted misspelled word. Note that the "Lock Pos" control is no longer available.

    Run-time Master: No Need to Enable

    The requirement for using Enable Run-time Master has been removed. The Run-time disks can now be used immediately after copying the files. The Enable Run-time Master command still appears on the Special menu, but is disabled.

    Edit Menu Always Available

    The Edit menu now always appears, even when no textbase is open.

    WebPublisher - Choices Droplists

    When you use DB/TextWorks version 4.2 to export your query screens to HTML, WebPublisher choices droplists now do a term search (exact match) instead of a phrase search.

    Feature for use with WebPublisher

    Ability to Search Multiple Textbases

    The Query Screen Designer now has the WebPublisher Multiple Textbase Query option on the Tools menu. You use this dialog to specify the necessary settings for WebPublisher to search multiple textbases. First you indicate that the current textbase is the lead textbase. Then you Add the other textbases you want to search to a list, and map fields in the other textbases to fields in the current query screen. (Note that only primary textbase fields can be mapped.) You can also specify which report and expanded display form to use for each textbase. When you export the query screen to HTML, the file will contain the necessary codes for WebPublisher.

    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.


    Version 4.1 Each feature is discussed briefly here. See the DB/TextWorks online help for more information. Note: There were no new features or feature changes in version 4.04.

    Version 4.1 - New Features

    Installation (and Run-time Version)

    Setup Workstation installs several files and registry entries necessary in order for DB/TextWorks to run properly.

    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

    Thesaurus

    The new Thesaurus feature enables you to:

  • create and maintain hierarchical thesauri (RT, NT, BT, USE & UF relationships are available).
  • browse and paste from the thesaurus in the Query, Edit or Edit Secondary Record windows
  • Reciprocity is maintained automatically (If term A points to B, then term B must point to Term A).

    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.

    Live Hypertext Links

    There's a new option on the Display tab of the Tools dialog:

    - 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.

    Send Report as Mail (SMTP)

    A new EMail tab on the Options dialog permits you to select whether Send Report as Mail should use MAPI (Messaging API) or SMTP (Simple Mail Transfer Protocol). Depending on which you select, choosing Send Report as Mail brings up the appropriate dialog. The SMTP version of the dialog has additional boxes to specify From, To, Cc and Bcc addresses, since SMTP bypasses your email client.

    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.

    Scripting - Menu Commands

    Many of the menu commands can be invoked from within a script. For a complete list, see the online help. The software will behave just as if the user selected that command from a menu. For example, this script calls Fit Window to Form when you open the window (and works for all windows: Query, Menu Screen, Report, Edit, etc.):

    function onFormOpen()
    {
      Command.fitWindowToForm();
    }
    For a few commands, the script can pass parameters to the menu command. For example, you can export the records in a set to a file without bringing up the dialog box that asks for the file name.

    Scripting - onFocus(), onBlur() and more

    Three new script triggers have been added:

    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();
    }

    Scripting - Sort Descriptor Object

    You can use a script to change the current user-specified sort (the sort specified using Display>Sort Report). For example, you can add Report Header buttons to the form you use in your Report window to sort the report by different fields. See the online help for more information and a sample script.

    Scripting - Form Script Dialog

    The Form Script and Screen Script dialogs in the designers are now resizable, and the size is retained from session to session. You can make them larger to see more of your script at a time.

    Menu Designer: Initial Action = HTML Application Window

    The Initial Action tab of the Box Properties dialog has a new option. You can specify that when you open the textbase, DB/TextWorks should open a specific HTML Application window instead of the Query window. The HTML Application Windows for an individual textbase are specified in the textbase INI file. See the online help for more information. This feature will be used in a new version of DB/Text for Libraries to simplify complex tasks.

    Write Report to File (Plain Text) - Indentation

    Write Report to File in Plain Text format now uses the indentation specified in the form, including hanging indentation. This feature is especially useful for designing forms which write information in Inmagic Tagged format.

    Import (Delimited ASCII) - Exception File

    If you import in Delimited ASCII and select "First Row Contains Field Names", if any records are rejected, the row containing the field name is now copied to the beginning of the exception file. So once you correct the problems which caused the records to be rejected, you can import the file.

    Version 4.03

    Note: Most of the changes in version 4.03 concerned addressing issues unrelated to new features.

    Version 4.03 - New Features

    New Quick Key

    Edit Secondary Record now has a quick key: Alt+F2.

    Toolbars

    Insert Current Date can now be added to the Main toolbar.

    Version 4.03 - Feature Change

    Installation

    Install and Setup Workstation now detect whether the machine is running Windows 95 or Windows 98. If so and no V4Repair= line is already present, V4Repair=1 is automatically added to the [Inmagic DB/TextWorks] section of the INMAGIC.INI file in the Windows directory. V4Repair=1 is a workaround for a problem encountered on specific (usually OEM) Windows 95/98 operating systems.

    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.


    Version 4.02

    Note: There were no new features or feature changes in version 4.01.

    Version 4.02 - New Feature

    Improved Print Preview

    Print Preview is now available, and includes improved functionality like the ability to zoom to view the page at actual size.

    Version 4.02 - Feature Changes

    Print & Form Orientation

    Print (and Print Preview) now automatically use the Orientation specified in the form.

    Print & Report Formatting

    If the Report window is still formatting when you choose Print (or Print Preview), you are asked if you want to stop the report formatting so the Print operation can proceed. If you respond No, the Print operation is canceled and the Report window continues formatting.

    Version 4.0

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information.

    Version 4.0 - New Features

    Form/Query Screen/Menu Designer Features

    The three designers have many new features.

    Form Designer Features

    These new features are specific to the Form Designer.

    Query/Menu Screen Designer Features

    These new features are specific to the Menu Screen Designer and the Query Screen Designer:

    Menu Screen Designer Features

    These new features are specific to the Menu Screen Designer:

    Basic Form Defaults

    The More Defaults button on the Display tab of the Options dialog permits you to specify several options (e.g., label position, box width, box and background colors, etc.) for the Basic Record Form, Basic Report Form and Basic Query Screen. The options on the General tab also affect menu screens.

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

    Search: Today's Date Variable

    You can now include the @DATE variable as part of your search criteria. When the search is performed, @DATE will be translated to the current date. You can also perform calculations using the @DATE variable. For example: @DATE -7.

    Send Report as Mail

    The new "Send Report as Mail" command on the File menu permits you to send the current report as an electronic mail attachment in a variety of formats (Plain Text, Rich Text Format, HTML). You also have the option of including a report in Plain Text format in the body of the message. Depending on the email program used to send/receive the message, HTML attachments may appear in the body of the message.

    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.

    Recover Textbase

    The new Recover Textbase choice on the Manage Textbases menu encapsulates the textbase recovery process. All you have to do is specify the name of the textbase you recover, and type the Master password (if any). Recover Textbase then dumps that textbase, creates a new textbase by copying the structure of the existing textbase, and loads the dump file into the new textbase. The original textbase is renamed.

    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.

    Applications Menu

    You can add an additional Applications menu to DB/TextWorks. This menu contains links to HTML pages. Which links appear on this menu is specified for each textbase. Choosing one of the options on this menu opens the HTML page in a window inside DB/TextWorks. All of the normal HTML behavior will work in this window: JavaScript, links, etc.

    Mouse Right+Click Menus

    Throughout the product you can now right+click with the mouse to perform such operations as Cut, Copy & Paste.

    Specify Window for Search Results

    After a search, you are prompted to specify which window to display the search results in: Report, Edit, or Display. You can choose not to display this message, so that records are automatically displayed in the selected window without asking. Previous versions only asked if you wanted to display the report.

    Image Printing - Xionics XipPrint

    Use XipPrint=1 in the [Imaging] section of INMAGIC.INI to take advantage of Xionics XipPrint enabled printers. This feature should speed up printing for black and white TIFF images. (This option has not been proven to work with all XipPrint enabled printers.) Use the FastPrint=1 option for color images.

    Report Window - Copy & Find

    Edit>Copy and Edit>Find are now available for the Report window.

    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.

    Copy - Retains Font

    Edit>Copy now retains the font of the copied information (often called Rich Text). When you paste into another application which supports multiple fonts, the font will be retained. Notes:

    3-Dimensional Box Borders

    Check "3-D box borders" on the Display tab of the Options dialog to use three-dimensional box borders in all forms and query screens.

    Search Highlighting

    You can now suppress search highlighting, for forms which have search highlighting enabled, without using the Form Designer to modify the form. Select "None" from either the "Display highlighting" or "Print highlighting" list on the Search tab of the Options dialog. For example: you can use the same form for both printing and displaying, without having your search terms highlighted in the printout.

    Recent Files - Specify Number of Textbases

    The new "Recently used file list" control on the General tab of the Options dialog permits you to specify how many recently-opened textbases to list on the Files menu. You can select a number between 0 and 10. Previous versions always showed 4 recently-opened textbases.

    Insert Entry Mark [F11]

    Press F11 or choose Insert Entry Mark from the Edit menu to break the current entry into two entries at the cursor position.

    Insert Date [F4] - Create New Entry

    The new "Insert date as new entry" control on the General tab of the Options dialog permits you to specify whether the inserted date should be created as a new entry (default behavior) or inserted into the current entry at the cursor position.

    Insert Series - Half Months

    A new Increment Unit option is available when using Insert Series in Date fields: Half Month.

    Date Formats

    This section discusses four optional DBTEXT.INI options which control date formatting in various places. Example:

    [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.

    - 0 means M-D-Y
    - 1 means D-M-Y
    - 2 means Y-M-D

    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
    
    This feature is especially useful when the Primary Month List includes months whose first three letters are the same (e.g., "juin" and "juillet" in French).

    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:

    Toolbar Features

    Customize Toolbar now has the option to add Separators to toolbars, so you can break toolbar buttons into groups.

    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.

    New "View" Menu

    The View menu permits you to control whether to display:

    - 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.

    Help Menu - Inmagic on the Web

    A new "Inmagic on the Web" section has been added to the Help menu. This pull-right menu includes choices for the Inmagic Home Page, the Inmagic Support Page and the Inmagic Product Support Knowledgebase page. Each of these choices launches your default web browser and loads the appropriate page. The Product Support Knowledgebase page was available in version 3.0.

    Resizing Dialogs

    Several of the dialogs can now be resized. This feature is probably most useful for the Query Choices Browser and the Editing Choices Browser. Now you can make the dialog wider so you can see more of long Titles, etc. The dialogs will revert to their default size the next time you use them.

    New Quick Keys

    Close (Textbase)- Ctrl+W
    Duplicate Record- Shift+F2
    Find- Ctrl+F
    New Query- Ctrl+Q
    New Textbase- Ctrl+N
    Omit Record- Alt+O
    Spell Check- F8

    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.


    Version 4.0 - Feature Changes

    Entry Marks

    In the Edit window, each entry now begins with a "Field entry delimiter" (by default, a bullet). You can use the Display tab of the Options dialog to specify which character to use. Important: The character used as the field entry delimiter should not be a character that will appear in the text of your record.

    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

    Print uses less 'leading' between lines, so that spacing is tighter than in earlier releases.

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

    Terminology & Menu Changes

    QBE Screens are now called Query Screens. Several menu choices have been renamed as a result (e.g., "Query by Example" on the Search menu is now "Query Screen").

    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:

    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.

    Saved Queries & Command Query Windows

    The Save Queries and Command Query windows now resemble dialogs in some ways. Each has text buttons (e.g., Execute Query) as well as toolbar buttons. In the Saved Queries window, the list of saved sets is a standard picklist control, so you can type the first letter to easily jump to a specific saved query in the list. In previous versions, you used Tab and Shift-Tab to navigate to different saved sets.

    Dialog Changes

    Several of the options on the designer Tool menu (Box Contents, Labels and Borders, Text Formatting, Paragraph Formatting, etc.) have been combined into a single tab dialog.

    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.

    "Smart" Scroll Bars

    Scroll bars on boxes in forms and Query screens don't appear until they are needed (i.e., until the amount of text in the box exceeds the maximum height of the box). Previous versions always displayed scroll bars on boxes that had them.

    Mouse and Cursor Position

    The cursor will appear where you click with the mouse (e.g., in the Display, Edit and Query windows). Previous versions put the cursor in the last cursor position for that box, or at the beginning of the box if this was the first time you'd clicked in that box since the window was opened.

    Edit Record & Passwords

    Boxes which are read-only due to password protection on the single field in the box now retain form formatting (e.g., item numbering). Previous versions removed formatting on boxes containing a single field, regardless of whether the settings for the current password.

    Customize Toolbars

    Toolbar customizations are now stored in the Windows Registry. Previous versions stored this information in the INMAGIC.INI file. You will need to redo any toolbar customizations created using earlier versions.

    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.

    Recent Files Changes

    The list of recently opened textbases is now stored in the Windows Registry. Previous versions stored this information in the INMAGIC.INI file.

    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.

    Open "Already Open" Textbase

    For previous versions, if you opened a textbase which was already open, DB/TextWorks closed and reopened the textbase (closed all windows and prompted for the password, if any). Version 4.0 simply leaves the textbase open. If you want to change passwords, choose Use Different Password from the File menu. If you want to close all windows except the initial window, choose New Query or close and reopen the textbase.

    Version 4.0 - Removed Features These features were available in previous versions, but are not available in version 4.0.

    Print Preview

    Print Preview is not available in version 4.0. The menu choice appears but is disabled.

    Designers

    Duplicate Box - use Copy & Paste instead.

    Form Designer

    Full justification. Forms created with earlier versions using this option will use Left justification instead.

    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.

    Edit Record

    Paragraph symbols no longer appear in the Edit Record window. Instead, paragraphs and entries use hanging indentation. Each entry begins with the "Field entry delimiter" specified using Options>Display.

    Customize Toolbars

    Use Large Buttons is no longer available in the user interface. However, you can use the LargeButtons=1 option in the INMAGIC.INI file to have toolbars use large buttons.

    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.

    Write Report to File>Plain Text

    Indentation and Justification specified in the form are currently ignored when writing information in Plain Text format.

    Messages

    Several warning messages have been replaced with beeps. For example: "You cannot enter or change information here."

    Find/Replace

    The "Match whole word only" control on the Find and Replace dialogs is no longer available for Textbase Information, the various View File windows, and Command Query. This control remains available for Edit Record & Batch Modify.

    Version 3.1

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information.

    Version 3.1 - Feature Changes

    Textbase Information Shows User Dictionary Location

    Display>Textbase Information now shows the location of the spell check user dictionary. The new line appears immediately under the line showing the user file directory.

    Export Menu Screen to HTML - HTML Title Changed

    When you exported a menu screen to HTML, previous versions used the HTML Title "Turbo Searches". Version 3.1 uses the HTML Title "Inmagic DB/Text WebPublisher Search".

    HTML QBEs with Word Wheels & FrontPage 98

    If you use FrontPage 98 to edit an HTML QBE screen with Word Wheels exported with DB/TextWorks version 3.0, FrontPage does not recognize the <APPLET> codes and discards all the associated <PARAM> and </APPLET> codes, making the QBE screen non-functional. Export QBE Screen to HTML for DB/TextWorks version 3.1 adds "protective" HTML comments around the <APPLET> codes, making the page more resistant to damage by FrontPage 98.

    Version 3.0

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information.

    Version 3.0 - New Features

    Spell Check

    Spell Check is available on the Tools menu when the Edit Record or Edit Secondary Record window is the active window.

    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).

    Searching for Extended Characters

    A new User Preference permits you to search for characters with diacritic marks (known as "extended" or "accented" characters) by typing the non-extended equivalent. For example, a search for "ole" will now retrieve "OLE", "Olé", etc.

    Copy/Delete/Rename Textbase

    Three new choices on the new Manage Textbases menu permit you to copy, delete, or rename a textbase in a single step. If the source and target locations differ for a Rename Textbase operation, the textbase is moved. These operations require exclusive access to the textbase. For example, you cannot delete a textbase someone else has open. If the textbase has passwords, these operations require the Master password.

    Window Size/Position Retained

    DB/TextWorks now preserves the size, position and maximization of all windows for each textbase. Previous versions retained only the size and position of the three image-related windows: Images, Image Annotation and Thumbnail.

    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.

    Window Synchronization

    Automatic window synchronization is now available. When you choose Synchronize Windows, all windows will be set to the selected record in the current window. When you press Next/Previous Record, etc. the same record will be displayed in all windows (e.g., Report, Display, Edit, Images). You can now easily scroll through the records with the record information and the image displayed side by side. For previous versions, Synchronize Windows was a one-time operation which reset all windows to show the same record, but did not keep the windows synchronized when you chose Next Record, etc.

    Import/Export/Batch Modify Options Retained

    DB/TextWorks now preserves the settings for the Import, Export and Batch Modify Options dialogs for each textbase. This information is stored in a <textbase>.IDI file in the user file directory.

    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.

    Image Annotation Path Retained

    The default location for image annotations is now preserved from session to session. This setting is separate for each textbase, and is stored in the <textbase>.INI file, so it affects all users who open that textbase. If the textbase directory is write-protected (e.g., on a CD), this information is stored in the <textbase>.IDI file in the user file directory. Previous versions always defaulted to the same directory as the image.

    Images on Multiple Drives/Volumes

    The two features described in this section enable you to access images on multiple CDs more easily.

    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:

    New Textbase - Copy Private Elements

    When you use New Textbase/Copy an Existing Inmagic DB/TextWorks Structure, there's a new check box which permits you to copy private forms, etc. stored in the user file to the user file for the new textbase. For previous versions, you had to copy the user file manually outside of DB/TextWorks.

    Menu Screen Designer - Open Current

    When you choose Design from the Menu Screens option, there's a new option to edit the current menu screen. For previous versions, you had to choose Open an Existing Menu Screen and specify the file name.

    Export in Sorted Order

    You can now export in sorted order. There must be a current set; to export the entire textbase in sorted order use Find All Records to create the set. There must be a current user-specified sort; at minimum, you must choose Sort and press OK. Use Current Sort is on the Records to Export tab. To enable it, select Export Current Set.

    Copy Special in Sorted Order

    Copy Special can now copy information to the Windows Clipboard in sorted order. Previous versions used internal record number order. Add the following line to the <textbase>.INI file:

    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).

    Additional Copy Special Button

    Two Copy Special buttons are now available. Add an additional [SpecialVendor2] section to <textbase>.INI using the same syntax. The Copy Special menu choices now always appear on the Tools menu in addition to being available for addition to various toolbars.

    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
    

    Accept Dates in YYYYMMDD and YYYY-MM-DD Format

    YYYYMMDD is now recognized as a valid date format. Previous versions indexed this format properly only if you unchecked "Numbers File Numerically' for the Date field in Edit Textbase Structure, and would not accept dates in this format in a Date field marked "Require Strictly Correct Type".

    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).

    New "Display Current" Menu Screen Option

    There's a new option on the Menu Screens menu: Display Current. This allows you to open your menu screen if you close it. In previous versions, you'd have to use Select Menu Screen and re-select your menu screen, or exit DB/TextWorks and re-enter, or open and close a textbase.

    Product Support Knowledge Base

    A new Knowledgebase option on the Help menu launches your web browser and loads the Inmagic Product Support Knowledge Base page. Here you can search for answers to frequently asked questions, helpful tips and tricks, software patches for download, etc.

    Version 3.0 - Feature Changes

    New "Manage Textbases" Menu

    There's a new menu when no textbases are open: Manage Textbases. The Dump Textbase, Load New Textbase, Check Textbase, and View Check Textbase Report File options have been moved to this menu. This menu also contains the new Copy Textbase, Rename Textbase, and Delete Textbase menu choices.

    Other Menu Changes

    User Preferences and Customize Toolbars, which used to appear on the File menu have been moved to the new Tools menu. This menu also includes the Spell Check option.

    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.

    "Unlimited" Boxes Taller

    Boxes set to have Max Lines of "unlimited" are now approximately the height of the screen. This includes both boxes in the Display/Edit windows and boxes on such windows as the Textbase Information and View Log File windows. In earlier versions, the box height was approximately 20 lines with the default font/box width, and varied as these settings changed.

    Larger Menu Screens, Textbase Elements

    Previous versions would display a message like "The form exceeds the maximum allowed storage space." if a form, menu screen, or QBE screen exceeded 64K. You could not save the form until it did not exceed 64K.

    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.

    Textbase Information - Current Forms, etc.

    Textbase Information now indicates if the forms, QBE screen, and record skeleton currently in use are private. The "Currently in Use" section appends "(private)" after elements stored in the user file. If "(private)" does not appear, the form is a public form, stored in the textbase.

    Form Designer - Label Forms

    Report Options/Set Up Page for label forms now permits up to 20 labels across. The previous limit was 10.

    Version 3.0 - Features for use with DB/Text WebPublisher 3.0

    HTML QBE and menu screens for use with version 3.0 of WebPublisher are completely different than those for previous versions. If you're upgrading from a previous version of WebPublisher, you must use DB/TextWorks version 3.0 or later to re-export any QBE and menu screens created for use with the earlier version. However, WebPublisher 3.0 is completely independent of previous versions. It's installed in a different location and has different names for the program files. So you can run both versions of WebPublisher simultaneously and make the transition to the new version gradually.

    If you have not upgraded to WebPublisher 3.0, you cannot use any of the following features. You must also use DB/TextWorks version 2.3 or earlier to export QBE screens to HTML for use with older versions of WebPublisher. DB/TextWorks version 2.3 (for Windows 3.x) is included as part of the DB/TextWorks version 3.0 installation.

    Position of Next/Previous Record Buttons

    Version 3.0 lets you specify whether you want the Next N Records and Previous N Records buttons and the list of available forms to appear at the top of the page, the bottom of the page or both. This control is on the Number of Records panel of the HTML Options dialog in the Menu and QBE Screen Designers.

    WebPublisher Form List

    Previous versions required that you select a form from the list then press the Change Form button. The Change Form button has been removed; simply selecting a new form in the list changes the display.

    WebPublisher Links

    A new WebPublisher Links panel on the Text Formatting dialog in the Form Designer permits you to treat each entry in a field as:

    Word Wheel - Scroll Bars

    The Word Wheel now has scroll bars for 4.x or later versions of Netscape or Internet Explorer.

    Word Wheel - Show Term Index

    You can now specify that the Word Wheel should display the Term index first. Check the "Show Terms by Default" control on the Browse Choices panel of the HTML Options dialog in the QBE Screen Designer.

    New WebPublisher Directory Structure

    The directory structure for WebPublisher has changed completely. Now, all WebPublisher files are installed in a virtual directory. This restructuring makes many of the following features available.

    HTTPS/Secure Socket Layers

    WebPublisher now works with Secure Socket Layers (SSL), which uses HTTPS:// instead of HTTP://.

    Export QBE/Menu to HTML

    You no longer need to specify your server name and program directory every time you export a QBE screen or menu screen to HTML. Instead, this information is stored in a file on your HTTP server.

    Textbase Path/Search

    The textbase path is no longer hardcoded into the HTML QBE screen (or menu screen). Instead, the first time a textbase is searched using WebPublisher, it will recursively search a set of directories specified during installation. When the textbase is found, the location will be written to the INMAGIC.INI file. Alternatively, you can edit the INMAGIC.INI file by hand to specify the textbase locations. See the WebPublisher README file for more information.

    Images in a Virtual Directory or Subdirectory

    Images can now be stored in a virtual directory or subdirectory. This includes both fixed images (e.g., backgrounds, and leading/trailing logos) and textbase images. Previous versions required that all images reside in the root directory of your HTTP server. See the WebPublisher README file for more information.

    Version 2.2a

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information.

    Version 2.2a - Feature Change

    4096 Characters of Fixed/Added Text

    In the Form Designer, each Fixed Text or Added Text (Beginning/Ending, etc.) string can now include up to 4096 characters. The previous limit was 250 characters.

    Version 2.2

    The feature changes in version 2.2 are primarily useful in conjunction with DB/Text WebPublisher and/or the DB/Text Intranet Spider.

    Version 2.2 - Feature Changes

    Using FrontPage on QBE Screens Exported to HTML

    Microsoft FrontPage rearranges hidden text in an HTML file even if all you do is open the file and save it. In earlier versions of DB/Text WebPublisher, the position of this hidden text was important. Both WebPublisher and Export QBE Screen to HTML have been made more robust so that using FrontPage does not make the HTML page unusable.

    Import Document - Field for File Name

    For earlier versions of DB/TextWorks, the "Field for File Name" droplist showed only Text fields. Since the field containing the file name (the URL field) in the DB/Text Intranet Spider textbase is a Code field, this list now shows both Text fields and Code fields.

    Dual Installation - 16-bit and Windows 95/NT Version

    The installation program now offers the option to install both the Windows 3.x (16-bit) version and the Windows 95/NT (32-bit) version in the same directory. In situations where some workstations have not yet been upgraded to Windows 95 or Windows NT, this enables each workstation to use the appropriate version of DB/TextWorks.

    Version 2.1

    Many of the new features in version 2.1 are primarily useful in conjunction with DB/Text WebPublisher. Each feature is discussed briefly here. See the DB/TextWorks online help for more information on these new features.

    Version 2.1 - New Features

    Query Choices Browser

    When viewing the word index for a Text field, the list now automatically jumps past the numeric entries to the first alphabetic word in the index. Term indexes and the word indexes for other field types (e.g., Date fields) still start with the selection at the top of the index.

    Searching - Require Spaces around Operators

    A new INMAGIC.INI option permits you to specify that certain "significant" characters must have spaces around them in order to be interpreted as search operators (e.g., Boolean AND, OR, NOT). If you set SpacedRelOps=1 in the [Inmagic DB/TextWorks] section, the following characters will not be interpreted as search operators unless surrounded by spaces: colon (:), forward slash (/), ampersand (&), and exclamation point (!).

    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
    
    To do an OR or range search, you'd need to put spaces around the symbols:

    cat / dog / fish
    1 : 25
    

    Version 2.1 - Feature Changes

    "HTML Reports" & "HTML Only Reports" Renamed

    In versions 1.3 and 2.0, when you saved a form, the "This Form can be Used In" section of the Save Form As dialog included two options: "HTML Reports" and "HTML Reports Only". If the current Report Window form was not saved as an HTML Report, Write Report to File in HTML would use the Basic Report form instead.

    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.

    Number of Records for WebPublisher Reports

    The Number of Records setting on the HTML Options dialog in the Menu and QBE Screen Designers permits you to specify how many records WebPublisher will display per page. The default setting has been changed to 20 records. In earlier versions, the default was "unlimited".

    Import - Inmagic Tagged Format Line Length

    The maximum permissible line length for Inmagic Tagged Format has been increased to 1024 characters. The earlier limit was 250 characters.

    Version 2.1 - Features for use with DB/Text WebPublisher

    Word Wheel

    You can now export QBE Screens which include the necessary commands to launch a Java applet which will permit end-users to browse the indexes using their Web browser. The Word Wheel dialog closely resembles the Query Choices Browser in Inmagic DB/TextWorks. The Word Wheel feature is discussed in more detail in the online help.

    Choices Droplist

    As an alternative to a word wheel, for fields with a short, static list of entries (e.g., a validated field), you can create a QBE screen with a droplist. Choices droplists can be used with Web browsers which do not support Java (e.g., Lynx).

    ISAPI or CGI

    When you export a QBE Screen or Menu Screen to HTML, you can now specify a Program Type of CGI or ISAPI, depending on which protocol your HTTP server software is using.

    "Change Form" Button and Picklist

    When you export a menu or QBE screen to HTML, you can now disable the Change Form button and picklist on the Report and expanded Display HTML pages. WebPublisher will use the form you specify and users will not be able to change to a different form.

    Page Background (HTML)

    You can now specify a background color or image for use with WebPublisher or Write Report to File in HTML. The new feature is on the HTML Options tool dialog in each of the designers.

    WebPublisher QBE Screen Help Link

    The QBE page Help link in previous versions was a simple Help text link. Now the Help link uses HELP.GIF, which you may replace with your own help icon if you prefer.

    Version 2.0

    Each feature is discussed briefly here. See the DB/TextWorks online help for more information on these new features. Be sure to read Application Window Size & Position in the "Version 2.0 - Feature Changes" section.

    Note: Version 1.3 was shipped only to clients who purchased DB/Text WebPublisher. If you are upgrading from version 1.2, also review the Version 1.3 section.

    Version 2.0 - New Features

    New Field Type - Automatic ID

    Fans of the "plus key" functionality for INMAGIC Plus record ID fields will appreciate the new Automatic ID field type.

    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").

    Edit Secondary Record

    When working in a textbase which has Link fields, you now have the option of editing and creating records in the associated secondary textbase. This topic is discussed extensively in the online help. Additional notes:

    Use Different Secondary Textbase Password

    Earlier versions required that if a secondary textbase had any passwords, a Silent password was required if you wanted to link to that textbase. This requirement has been removed.

    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.

    Write Report to File

    Once you have performed a search, you can now write the report to a file using the formatting for the selected Report Window form. You can do this in one of three formats:

    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:

    Copy Report to Clipboard

    This new menu choice copies the current report to the Windows Clipboard in plain text form, using the selected Report Window form. You cannot copy more than 64K to the Clipboard. You do not have to display the report before copying it to the Clipboard.

    Copy Record to Clipboard

    This new menu choice copies the selected record to the Windows Clipboard using the form for the current window. For example, if you use this feature while editing a record, the current Edit form will be used.

    Annotate Images

    You can add text and graphics to an image to mark it up, treating the image as a sheet of paper. The annotation is a separate file, layered on top of the original image file, which remains unchanged. Images can be displayed and printed with or without annotations.

    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.

    Scan Images (TWAIN)

    While editing a record, you can now scan an image and automatically paste the file name into the Image field. Any TWAIN-compatible scanner will work. Note that this feature doesn't support automatic document feeders.

    Images - Focused Zoom

    When the mouse cursor is over the Images or Image Annotation window, it turns into a magnifying glass. When you click the mouse button, the image zooms in around that point. Compare with the Zoom In and Zoom Out menu choices.

    Images - Deskew & Despeckle

    There are two new options in the bottom section of the Images menu:

    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.

    Year 2000 Customization

    As the year 2000 approaches, many people are concerned about how various software packages will treat dates with 2-digit years (such as 01-May-96). Note that this issue does not affect 4-digit years. For 2-digit years, there is a new setting in the DBTEXT.INI file for specifying the first year in the current century, with the default being 1900 (for backward-compatibility).

    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.

    Import - View Exception File

    If records are rejected during an Import or Load New Textbase operation, DB/TextWorks now automatically displays the exception file when you press OK on the completion message.

    Delimited ASCII Import/Export

    You can now specify the Quote Character (including {NONE}) during delimited ASCII import and/or export. In previous versions, the quote character was always assumed to be double quote (").

    Import Document - HTML Documents

    If you have DB/Text Import Filter installed, but want to import HTML documents retaining all the HTML codes, choose Import Method on the Import Options dialog and uncheck Use Word Processing Filter.

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

    Menu Designer - Remove Icon

    The Icon section of the Box Contents dialog now has a Remove Icon button. Earlier versions had no way to remove a menu icon once it had been attached to a box.

    Help on this Window Button

    The toolbar for each DB/TextWorks window now includes a new "Help on this Window" button. Pressing this button will bring up help for the current window. For example: If you press the "Help on this Window" button on the menu screen toolbar you bring up the help topic entitled "Opening a Textbase Using a Menu Screen".

    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.

    Textbase Structure Backup and Restore

    There's a new button on the Edit Textbase Structure dialog: Back Up Structure. This feature writes the structure definition to a plain text file (extension .TBB). This file includes all information except the records and the image annotation list (use Dump Textbase to back up these). Passwords are encrypted but most of the other information is not, so you may want to consider keeping these files in a secure location.

    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.

    Dump/Load New Textbase - Image Annotation List

    The file created by Dump Textbase now includes the Image Annotation List at the end of the file, separated from the records by a line containing three colons (:::).

    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.

    Check Textbase

    If there are problems with the textbase:

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


    Version 2.0 - Feature Changes

    Application Window Size & Position

    In previous versions, the DB/TextWorks Application window always started out maximized. Starting with v2.0, the Application window complies with the settings on your program item properties. If the setting is "Normal window", DB/TextWorks will use the size, position and window setting (maximized, normal, or minimized) from the last time you exited DB/TextWorks. This information is saved in the INMAGIC.INI 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.

    Renamed Menu Choices

    The following menu choices have been renamed for clarity:

    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.

    Toggling Menu Choices

    Many of the menu choices which used to be checked or unchecked depending on whether the feature was active now toggle the menu text instead. For example, the "Show Boundaries" menu choice in the Form Designer now toggles between Show Boundaries and Hide Boundaries, depending on whether boundaries are currently visible.

    Dialog Box Changes

    The Win95/NT version uses "tab" dialogs in several locations. Examples: User Preferences, Text Formatting in the Form Designer.

    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.

    Maximum Textbase Users

    When you create a new textbase, version 2.0 automatically sets the number of users permitted to open a textbase simultaneously to the number of licensed users or 25, whichever is higher. This change will not affect existing textbases. The top-level Edit Textbase Structure dialog now displays the "Maximum textbase users" setting.

    Title Bar - Opening Textbase Read-Only

    When you open a textbase read-only, or open a write-protected textbase, the title bar now says <Read-Only> in the place where the indexing mode (e.g., <Shared Immediate>) usually appears. Earlier versions said <None>.

    WebPublisher Features

    When you export a menu screen or QBE screen to HTML, the last-used Server Name and CGI Directory are automatically read from the INMAGIC.INI file.

    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.


    Version 1.3

    Many of the new features in version 1.3 are primarily useful in conjunction with DB/Text WebPublisher. Each feature is discussed briefly here. See the DB/TextWorks online help for more information on these new features.

    Version 1.3 - New Features

    Tabular Forms

    The Open Form dialog in the Form Designer has a new initial form type: New Tabular Form.

    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.

    Write Report to HTML

    Once you have performed a search, you can now write the report to HTML using the formatting for the current Report Window form. This feature is useful for generating static intranet or Internet Web pages. When your records change, you'll need to use this option again to update the HTML document. DB/Text WebPublisher provides dynamic access to your DB/TextWorks textbases using browsers like Netscape and Microsoft's Internet Explorer.

    Saved Queries Window

    The new Saved Queries window lists all of the saved sets. When you click on a set, DB/TextWorks automatically performs the search. This is a shortcut for using Refresh Sets for a single set, or choosing Load Set from the Sets menu then choosing Execute Query from the Search menu. However, you cannot resave the set under the same name.

    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.

    Initial Action

    The Menu Screen Designer now permits you to specify what happens when you open the textbase. You can specify one of the following:

    NoneOpens 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 WindowOpens the specified window.
    Saved QueryPerforms the search specified in the saved query you choose.


    Version 1.3 - Feature Change

    Menu Screen Designer - Box Attributes Dialog

    To accommodate the new Initial Action feature, the Box Attributes dialog has been completely redesigned. The name has also been changed to Box Contents to match the other designers.

    Version 1.3 - Features for use with DB/Text WebPublisher

    Export Menu & QBE Screens

    You can use the "Export...to HTML" menu choice in the Menu Screen Designer and QBE Screen Designer to write out menu and QBE screens using HTML for use with DB/Text WebPublisher.

    HTML Options

    Each of the three designers has the new HTML Options menu choice on the Tools menu. This dialog permits you to specify various attributes of forms, QBE screens, and menu screens for use with DB/Text WebPublisher.

    Version 1.2

    Version 1.2 - New Features

    Saving Records

    You can now specify how DB/TextWorks will respond if you cannot save a record in Shared Immediate mode because others are using the index. See the SwitchDeferredOption= INMAGIC.INI option. (SwitchDeferredOption= is now available as "If indexes are busy:" on the Deferred Indexing section of Tools>Options>General.)

    Designers - Tab Order

    The Tab Order dialog in the Form, QBE and Menu Designers now has a new button called "Reset to Default Tab Order". Pressing the button sets the tab order to the order in which the boxes are drawn on the screen.

    Interrupting Report Formatting

    If you interrupt the formatting of a report (by pressing [Esc] or the STOP button), the following text appears after the last record as a reminder:

    *** REPORT INTERRUPTED ***

    Import Document

    You can now select up to 5000 documents for a single Import Document operation. If you select more than 5000 files on the Select Document Files dialog, you receive an error message.

    Multi-Image TIFF Files

    DB/TextWorks now displays and prints all the images in multi-image TIFF files.

    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.

    Fast Image Printing

    A new INMAGIC.INI option can significantly increase image printing performance. See the FastPrint=1 option in the "INMAGIC.INI Entries" section. "Fast image printing" may not work with all images or all printers.

    Sorted Image Printing

    If you print images with the Report window open and select "Print Images in Current Set", now the images will be printed in the order in which the records have been sorted in the report. Formerly, the image printing order did not necessarily match the order of the records in the report.

    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.

    New Records - Image Printing

    You can now print the images in a newly created record, even before you have saved the new record.

    Image Counters

    You can now enclose the counter after an image file name in parentheses as you could in INMAGIC Plus for DOS. Both of the following formats are accepted:

    IMAGE.001 (3)
    IMAGE.001 3
    

    Populate New Computed Fields

    A new "Recompute Field Value" check box, on the Rebuild a Field Index dialog, permits you to populate computed fields in records where they are empty. For example, you may have just added a new computed field, or used Reload Textbase to import records which didn't include the computed field. (In version 2.0 Reload Textbase has been renamed Load New Textbase.)

    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.

    About DB/TextWorks

    The About DB/TextWorks dialog now has a Print button to make it easier for you to send your serial number and other information to Inmagic, Inc.

    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.

    Check Textbase

    Check Textbase (choose Diagnostic Support from the Special menu) now reports if the keys in any index are out of sequence. This will help you determine whether you are affected by changes in international filing if you move from Windows 3.x to Windows 95. The Check Textbase report may include lines like these (where <key> represents the entry which is out of order):

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

    Textbase Information

    Textbase Information (available from the Display menu) now includes the contents of the DBTEXT.INI file and any <textbase>.INI file at the bottom. This information is especially useful in diagnosing problems with Copy Special or Textbase-Specific Help.

    Copy Special

    When Copy Special is invoked from the Report window, a new <textbase>.INI option permits you to specify whether to copy information from all records in the set, or just the selected record. The default is to copy information from all records in the set. To copy information from just the selected record, specify MultipleRecs=0 in the [SpecialVendor] section. Example:

    [SpecialVendor]
    Vendor=launch
    SpecialField=Document
    MultipleRecs=0
    

    Textbase-Specific Help

    The name and path of any textbase-specific help file can now be specified in a new [Help] section of the <textbase>.INI file as follows:

    [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.

    Import Document - Word Processing Files

    If you purchase DB/Text Import Filter, a set of auxiliary DLLs for use with DB/TextWorks, you can use Import Document to directly import word processing, spreadsheet and HTML files created using such programs as Microsoft Word, WordPerfect, and Netscape. The program automatically detects the format of the document, so you can import documents from several different programs at the same time.

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

    Long File Names ("Win95/NT" version only)

    If you have the "Win95/NT" version of DB/TextWorks, you can use long file names for textbases, image names, and all other file names. See the DB/TextWorks help for more information.

    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.)


    Version 1.2 - Feature Changes

    Calculations - FCOUNT

    In version 1.1 and earlier, the FCOUNT function used on an empty field returned nothing (i.e., computed field was blank). Now it returns 0. So if you want to quickly find fields which are empty, you can now use the following procedure:

    1. Use Edit Textbase Structure to add a computed field whose formula uses the FCOUNT function on the field in which you want to find empties. Be sure to give the new field a Term index.
    2. Choose "Rebuild a Field Index", select the new computed field and check the new "Recompute Field Value" box.
    3. Search the new computed field for entries equal to zero (=0).

    Note that you can always find empties in a field by searching for NOT <fieldname> = *. However, this can be a lengthy search in a large textbase.

    Maximum Textbase Users

    When you created a new textbase, version 1.1 and earlier of DB/TextWorks automatically set the number of users permitted to open a textbase simultaneously to the number of users permitted to use the software. This has led to confusion when users purchased multi-user versions of DB/SearchWorks or multiple copies of DB/TextWorks. You could use the Maximum Users button on the Edit Textbase Structure dialog to change this value.

    Version 1.2 sets the maximum textbase users to the number of licensed users or 5, whichever is higher. Note that this change will not affect existing textbases. (In version 2.0, this number has been increased to 25 users.)

    DB/TestMAGIC

    The number of licensed users for DB/TestMAGIC has been increased from 5 to 30 to permit it to be used in a classroom or training environment.

    Formatting Reports

    A simple percentage-done indicator shows how much of the report has been formatted. This was changed from the bar used to measure the progress of other operations, to make it clearer that you need not wait until formatting is finished to begin navigating, editing records, displaying images, and so on.

    Recent Files

    The 4 most recently opened textbases used to be listed in INMAGIC.INI with the path and file name all on one line, indicated by File1= through File4=. To facilitate long file names in the Win95/NT version, the path and file name are now listed on separate lines. This means that the recent files listed under Exit on the File menu will be blank for users upgrading from version 1.1 until they have opened textbases using version 1.2.

    Extended Characters

    Search item highlighting, and phrase and proximity searching now handle extended characters better.

    Printing and Colors

    The background color of form boxes no longer affects printing. So you can have a background color other than white without having your printed reports appear as black text on a gray background.

    MOUSETRK.DLL

    Version 1.2 doesn't use this DLL file. You can delete it from the DB/TextWorks installation directory.

    Version 1.1

    Version 1.1 - New Feature

    Menu Screen Designer

    Version 1.1 introduced a new feature: Menu Screens. A menu screen is a front-end which allows users to open a textbase by choosing an option from the menu screen. For information on this new feature, search the Help for "menu screens".

    You can use the /m command line option to specify which menu screen to open when starting DB/TextWorks. The following example runs the 16-bit version of DB/TextWorks and opens the OPAC.TBM file in the C:\LIBRARY directory:

    Command Line: DBTEXT /M C:\LIBRARY\OPAC
    

    Critical Errors

    All DB/TextWorks messages are documented in the DB/TextWorks Messages textbase (DBTMSG) included in the Inmagic Applications group. However, there are several messages which may prevent you from starting the software or opening any textbase (including the messages textbase). Each is documented below. Messages are listed in alphabetic order.

    Cannot create directory '<directory>'.

    Either this is the first time you've run DB/TextWorks or you've deleted your UserFilePath setting in the INMAGIC.INI file for some reason (e.g., by renaming or deleting INMAGIC.INI).

    You typed a directory which doesn't already exist in the User File Path dialog, and responded Yes to the "Directory does not exist. Create it?" question. However, DB/TextWorks encountered an error when trying to create the directory.

    When you press OK, you return to the User File Path dialog so you can try again.

    Solution

    Verify that:

    Try creating the directory manually either using:

    If all else fails, accept the default that DB/TextWorks supplies (e.g., C:\WINDOWS). This directory will always exist and you will always have the necessary rights to create files there.

    Cannot open license file. Contact system administrator.

    This message will normally only occur for network installations. The DBTEXT.LIC file does not exist and you do not have the necessary rights to create it.

    Solution

    Have someone with write and create access to the directory containing the software run DB/TextWorks. For example: on a Novell network, have someone with SUPERVISOR or supervisor-equivalent access run DB/TextWorks.

    The license file will be created automatically.

    Cannot read 'dbtext32.cmx'

    This message can appear for one of two reasons:

    1. The DBTEXT32.CMX file is missing or damaged.
    2. You press OK on the Enable or Upgrade Network dialog when you don't have write access to the directory where DBTEXT32.CMX is located. To get to this dialog, you choose "Enable or Upgrade Network" from the Tools menu.

    When you press Cancel on the Enable or Upgrade Network dialog, you'll receive an "Error opening file DBTEXT32.CMX: Access denied." message.

    Solution

    If the DBTEXT32.CMX file is missing or damaged, reinstall Inmagic DB/TextWorks.

    Log in using a user id (e.g., SUPERVISOR on Novell Netware networks) which has full access to the directory where DB/TextWorks is installed before attempting to increase the number of licensed users.

    Notes

    If the DBTEXT32.CMX file is write-protected, you get an error message when you select Enable/Upgrade Network and press OK.

    Directory does not exist. Create it?

    Either this is the first time you've run DB/TextWorks or you've deleted your UserFilePath setting in the INMAGIC.INI file for some reason (e.g., by renaming or deleting INMAGIC.INI).

    You typed a directory which doesn't already exist in the User File Path dialog.

    Solution

    If this is the first time you've run DB/TextWorks and you want to create the new directory, choose Yes.

    If you already have existing user files, or you made a mistake when typing the directory name, choose No. You return to the User File Path dialog so you can specify the directory where your user files (extension .TBU) are already located.

    File '<file name>', and possibly other textbase files, no longer exist. The textbase cannot be opened.

    Please note that the 'Recover Textbase' operation may help you recover from this problem.

    You tried to open a textbase using one of the following methods:

    1. You clicked on a textbase box in a menu screen.
    2. You chose one of the "last-used" textbases from the bottom of the File menu.
    3. You chose Open from the File menu.
    4. You used Dump Textbase, Load New Textbase or Check Textbase on the Manage Textbases menu.

    DB/TextWorks cannot find the file name shown in the message.

    Solution

    If you used one of the first two methods, the problem may simply be that you've moved or renamed the textbase or are not connected to the network drive where the textbase is located. Or, the textbase may have been a temporary textbase that you've deleted because you no longer need it.

    If you used one of the second two methods, the problem is probably more serious. The .TBA file exists, but other files are missing. The Recover Textbase choice on the Manage Textbases menu will only be useful if all of the textbase files with the following extensions do still exist: .tba .dbs .dbr .dbo .acf. If not, your only recourse is to restore the textbase from a healthy backup.

    File '<file name>' cannot be read. It is possible that the file is corrupted.

    The file name shown in the message exists, but DB/TextWorks cannot read essential information in it. The file may be corrupted.

    Solution

    If the file is one of the files installed with DB/TextWorks (e.g., DBTEXT32.EXE, DBTEXT32.CMX, or a .DLL file), you can reinstall DB/TextWorks from the original disks.

    Sharing violations may also cause this message to appear. If you only receive this message when someone else already has the file open, you may need to use system commands to set the file to sharable read-only.

    File '<file name>' cannot be read. The file may be corrupted or an incorrect version of the Netware client is setup for Windows 95.

    DB/TextWorks has detected that you are running Windows 95. The file name shown in the message exists, but DB/TextWorks cannot read essential information in it. The file may be corrupted.

    Solution

    This message is most likely to occur if you have a Novell network and use the Microsoft Client for Netware under Windows 95. If this is the problem, you will only receive this message when someone else already has the file open. You have several options:

    If you don't have a Novell network, but only receive the message when another person already has the file open, try using system commands to set the attributes of the file to shareable, read-only.

    If this is not the problem, and the file is one of the files installed with DB/TextWorks (e.g., DBTEXT32.EXE, DBTEXT32.CMX, or a .DLL file), you can reinstall DB/TextWorks from the original disks.

    File '<file name>' is missing, and Inmagic DB/TextWorks cannot run. Please reinstall.

    DB/TextWorks checks for several files on startup, including DBTEXT32.CMX and certain DLL files. The file name shown in the message is missing.

    Solution

    Reinstall DB/TextWorks from the original disks using the SETUP program, and apply all subsequent patches (if appropriate). Or restore the missing file from a healthy backup.

    SHARE is not loaded. Please exit Windows and correct.

    You started DB/TextWorks when your system setup does not load any file-sharing and locking utilities (e.g., SHARE.EXE or VSHARE.386). You will not be able to run DB/TextWorks until you address this issue.

    Solution

    Exit Windows and load one of the utilities which enable file-sharing and locking for the version of Windows which you are using. Check your Windows documentation for more information.

    For Windows 3.1 or Windows for Workgroups 3.11, either:

    - (Preferred) Put VSHARE.386 in your C:\WINDOWS\SYSTEM directory and add DEVICE=VSHARE.386 to the [386Enh] section of your SYSTEM.INI file.

    - (Quick) Type SHARE at the DOS prompt before entering Windows. For a more permanent solution, add SHARE to your AUTOEXEC.BAT file or DEVICE=C:\DOS\SHARE.EXE to your CONFIG.SYS file.

    For Windows 95: File sharing should be loaded by default for Windows 95. Check your SYSTEM.INI file for the line DEVICE=VSHARE

    For Windows NT: Windows NT uses SHARE.EXE in the CONFIG.SYS file.

    Notes

    VSHARE.386 is installed by newer versions of Microsoft products (e.g., Word for Windows). It's also available in a self-extracting executable called WW1000.EXE available on both CompuServe (GO PCFF to find it) and the Internet (at ftp.microsoft.com).

    Software has an invalid serial number. Please reinstall.

    The serial number is not a valid Inmagic DB/TextWorks serial number. The most likely cause for this is that the DBTEXT32.EXE file has been damaged or the installation process failed prior to completion.

    Solution

    Reinstall DB/TextWorks from the original disks using the SETUP program, and apply all subsequent patches (if appropriate).

    Temporary directory has not been specified or is write protected, please specify a writable directory in the TEMP variable.

    You are running DB/TextWorks from write-protected media (e.g., a write-protected floppy or a CD-ROM). DB/TextWorks is trying to create a file in the default directory or the directory specified using the TEMP= environment variable.

    Solution

    Shell to DOS and type SET TEMP=C:\ or some other directory to which you have full access. Ideally, this environment variable should be set in your AUTOEXEC.BAT file.

    The textbase is not available because someone else has exclusive access. Please try again later.

    You tried to open a textbase when someone else has already has the textbase open with exclusive access. This can happen when:

    Solution

    Wait until the other person finishes using the textbase.

    Notes

    If this message appears frequently, you might want to:

    The user file path '<path>' specified in your INMAGIC.INI file does not exist.

    When you open or create a textbase, DB/TextWorks checks your user file directory for a matching user file for that textbase. If no user file exists, DB/TextWorks attempts to create one. However, the user file directory represented by '<path>' in the message does not exist, so DB/TextWorks cannot create a user file until you specify a new user file path.

    Solution

    When you press OK on the message, the User File Path dialog will appear, with the user file path specified in your INMAGIC.INI file filled in.

    If you'd like to create the user file path shown, press OK. Otherwise, specify a different user file path. For example, your INMAGIC.INI file might have been created by your network administrator and copied to everyone's Windows directory. If you know where your user files are located, specify that directory. User files have the extension .TBU.

    This is not the correct version of the DBTEXT32.CMX file. Please reinstall.

    The DBTEXT32.CMX file in the same directory as DBTEXT32.EXE is from an different version. When you press OK, you exit the software.

    Solution

    Reinstall DB/TextWorks from the original disks using the SETUP program, and apply all subsequent patches (if appropriate).

    You have reached the maximum number of users licensed (<number>). Please try again later. Contact Inmagic, Inc. to increase the number of users permitted.

    You tried to run Inmagic DB/TextWorks when the number of users allowed to run the program simultaneously (indicated by the number in parentheses) has already been reached. For example, if you have a 10 node license, you receive this message when the eleventh person tries to start the software.

    Solution

    You will be able to use Inmagic DB/TextWorks when someone else stops using it.

    If this message appears frequently, contact the Inmagic, Inc. Sales Department to increase the number of simultaneous users permitted.

    This message can also appear if a workstation (node) goes down (gets turned off or rebooted, or loses its network connection) while someone is using Inmagic DB/TextWorks on it. Most networks eventually time out and release the lock.

    Try logging in from the same workstation to release the connection. If the problem does not clear, contact your system administrator.

    Your workstation setup is out of date, and you must run Setup Workstation again on this machine before you can run Inmagic DB/TextWorks. See the Installation Notes for more information.

    You attempted to run DB/TextWorks when Setup Workstation has not been run on this machine. Setup Workstation doesn't simply create shortcuts; it installs files and registry entries necessary for DB/TextWorks to run.

    Solution

    On Windows NT machines, log in as Administrator.

    Then close down all other applications, including the Microsoft Office taskbar, and run Setup.exe from the directory when DB/TextWorks is installed. Click the Workstation button and follow the prompts.


    INMAGIC.INI Entries

    INMAGIC.INI is stored in each user's personal Windows directory and includes personal customizations and preference settings. Entries are listed by section. Entries which must be set by editing the INMAGIC.INI file (when neither DB/TextWorks nor DB/SearchWorks is open) are in italics; other options can be set using various DB/TextWorks controls and menu options. For options which show '=1', 1 turns the option on, 0 turns it off.

    [Inmagic DB/TextWorks]

    The following options always appear in this section of INMAGIC.INI:

    AutoReport= Controls Options>Display 'Always use this option without asking' 0 = Display the Select Search Results Window dialog (default)
    1 = Use selected window automatically without asking
    AutoReportOpt=Controls Options>Display 'After a search, view records in:' 0 = Report window (default)
    1 = Edit window
    2 = Display window
    3 = Do not display records
    AutoURLDetect= Controls Options>Display 'Detect URLs, EMail links, etc. and convert to hypertext links' 0 = Don't convert to hypertext links
    1 = Convert to hypertext links (default)
    CustomColor1=
       through
    CustomColor16=
    Stores the 16 custom colors that appear on the Colors dialog box.
    Edge3D=Controls Options>Display '3-D box borders' 0 = Do not use 3-D borders (default)
    1 = Use 3-D borders
    EmptyTBNotify=Controls Options>Display 'Notify when opening empty textbase' 0 = Don't display message when opening empty textbase
    1 = Display message when opening empty textbase (default)
    IgnoreAccents=Controls Options>Search 'Ignore accents on extended characters': 0 = Do not ignore accents when searching (default)
    1 = Ignore accents when searching
    Inclusive=Controls Options>Search 'Use inclusive search option for multiple fields': 0 = Do not use inclusive search option
    1 = Use inclusive search option (default)
    InitialWindow=Controls which window appears when you open a textbase (unless the menu screen in use specifies a different initial window): 1 = Query window (default)
    2 = Command Query window
    3 = Saved Queries window
    4 = Edit: New Record window
    Note: If the textbase contains no records, DB/TextWorks opens the Edit: New Record window regardless of which initial window is specified.
    InsertNewEntry=Controls Options>General 'Insert date as new entry' setting: 0 = Insert date at cursor position
    1 = Insert date as new entry (default)
    LargeButtons=Controls the size of toolbar buttons 0 = Do not use large buttons (default)
    1 = Use large buttons
    LDate=Controls Options>General 'Insert date using long format' setting: 0 = Use short date format (default)
    1 = Use long date format
    LinkP=Controls Options>General/Passwords 'Secondary Textbase' setting: 0 = Use Silent password and do not show warning (default)
    1 = Always prompt for password
    MaxMRU=Controls the number of recent textbases on the File menu (Options>General 'Recently used file list'). Default is 4.
    NewData=Controls Options>General/Deferred Indexing 'Show deferred changes in reports and display': 0 = Show old version of record (default)
    1 = Show record with deferred changes
    PrintUsing=Controls Options>General/Report options 'Always use this option without asking' 0 = Display the Form Used to Print Report dialog if Report/Display/Edit window active (default)
    1 = Use selected print form automatically without asking
    PrintUsingOpt=Controls Options>General/Report options 'Print using' form 0 = Use Report Printing form
    1 = Use form for active Report/Display/Edit window
    SilentP=Controls Options>General/Passwords 'Primary Textbase' setting: 1 = Use Silent password and show warning (default)
    2 = Use Silent password and do not show warning
    3 = Always prompt for password
    SortFieldLists=Controls Options>Display 'Sort textbase field lists alphabetically' setting: 0 = Field lists appear in textbase structure order (default)
    1 = Field lists are sorted alphabetically
    SMTPServerName=Name of SMTP server
    SMTPIPAddress1=
    SMTPIPAddress2=
    SMTPIPAddress3=
    SMTPIPAddress4=
    Four parts of the SMTP Server IP address
    SwitchDeferredOption=Controls Options>General/Deferred Indexing 'If indexes are busy' (how DB/TextWorks responds if you cannot save a record using Shared Immediate indexing): 1 = Doesn't save record and suggests switch to Deferred indexing
    2 = Saves record using Deferred indexing silently
    3 = Saves record using Deferred indexing and displays message (default)
    SynchWin=Controls the setting of Synchronize Windows on the Windows menu 0 = Do not synchronize windows (default)
    1 = Synchronize windows
    TabToQBEButton=Controls Options>Search 'Allow tabbing to Boolean query buttons': 0 = Tab skips AND/OR/NOT buttons. The only way to change the state of the buttons is with the mouse.
    1 = Tab moves to AND/OR/NOT buttons. Press the spacebar to change state of button. (default)
    TabToHTMLBoolean=Controls tabbing on query screens created using Export Query Screen to HTML: 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.
    TBMenu_Path=
    TBMenu_File=
    The directory and file name for the current menu screen. (Shows short file name for Win95/NT version).
    UserFilePath=Shows the user file path specified using the User File Path dialog the first time you started DB/TextWorks.
    UseSMTP=Controls Options>EMail 'Access EMail services using' 0 = use MAPI (default)
    1 = use SMTP

    The following options do not appear in INMAGIC.INI unless you add them explicitly using a text editor.

    ExpressImportBuffer=Normally, Express Import appropriates as much memory as possible to provide maximum speed. However, if you find Windows is swapping a lot when using Express Import, you can set the size of the import buffer. If you type 4096, then the buffer will be 4096 KB even if there is more memory available (and less if that much memory is not available).
    RptBorderWidth=Set the width of the selection box in the Report window. If you use this feature, the tops of characters may be whited out when you move the selection box off a record. A value somewhere between 3 and 5 will increase the visibility of the selection box without obscuring the records in the report.
    SpacedRelOps=Controls whether spaces are required around search operators (colon, slash, ampersand, etc.) 0 = Characters are always interpreted as search operators, e.g., Boolean OR (default)
    1 = Characters are only interpreted as search operators if surrounded by spaces
    V4Repair=Some older versions of Windows 95/98 (particularly OEM installs) may GPF upon displaying a box in version 4.x with multiple lines in it. Set V4Repair=1 to prevent the GPF. Note: Current versions of Setup Workstation automatically set V4Repair=1 if Windows 95 is detected.

    [Highlight]

    Display=Controls Options>Search 'Display highlighting': 1 = Reverse Video (default)
    2 = Color, in this case a Color= line also appears
    3 = None
    Printing=Controls Options>Search 'Print highlighting': 1 = Bold (default)
    2 = Italic
    3 = Bold Italic
    4 = Underline
    5 = None

    [Entry Mark Format]

    The 'Field entry delimiter' specified using Tools>Options>Display.

    [Box Font]

    The 'Text Font' specified using Tools>Options>Display.

    [Title Font]

    The 'Label Font' specified using Tools>Options>Display.

    [FormSettings]

    The default form and query screen settings (e.g., form and box background colors) specified using the Form Defaults dialog (Options>Display>More Defaults).

    [Designers]

    The location on the screen of the dialogs in the designers.

    [Imaging]

    Despeckle=10This number can be anywhere from 0 to 100, and specifies how aggressive the despeckling procedure should be. Higher numbers take out more extraneous dots, but may wind up taking out some real ones too if the image wasn't sharp to begin with.
    FastPrint=1Uses "fast image printing". May cause printer errors or hang with certain images or printers.
    ImageDrive=The 'Image drive(s)' shown under Tools>Options>Imaging.
    MultiplePageImage=Controls the Imaging option 'Support multiple page TIFF images': 0 = Only first image is displayed
    1 = All images are displayed (default)
    PreferenceFlags=0Causes Thumbnail window to use less memory. Aspect ratios may not be preserved.
    ScaleToGray=1Scale to Gray is checked for the Images, Image Annotation and Thumbnail windows.
    ThumbNailColumns=The Columns value specified using 'Set Rows and Columns' from the Thumbnail window.
    ThumbNailRows=The Rows value specified using 'Set Rows and Columns' from the Thumbnail window.
    Win3xFileName=Controls the Imaging preference 'Support only short filenames for images': 0 = Image file names can contain spaces (default)
    1 = Image file names cannot contain spaces
    Set this option to 1 only if you are using the Win95/NT version and existing Image fields contain text other than the number of images after the image file name.
    WinFitFlags=Controls the Imaging option 'Fit Image to Window'. Default value is 2 which corresponds to 'Scale Proportionally if Necessary' with 'Leave Small Images Original Size' off.
    XipPrint=1Takes advantage of Xionics XipPrint enabled printers.

    The following options reflect the current settings of the matching options on the Annotation Properties dialog in the Image Annotation editor:

    ArrowHeadStyle=Arrow Head Type
    BackColor=Background Color
    FillPattern=Fill Pattern
    FontFace=Font (default is Times New Roman)
    FontParams=Other font information, including size. DB/TextWorks makes a "best guess" for the font size the first time you annotate an image, then saves the specified font size.
    ForeColor=Foreground Color
    LineStyle=Line Style
    LineThickness=Line Thickness
    PaintMode=Background Mode

    [Window Placements]

    The window size, position and maximization settings for windows which are not textbase-specific (e.g., the Menu Screen or Textbase Information window).

    [WebPublisher]

    The following options affect Export Editing Form to HTML and Export Query Screen to HTML. You must exit DB/TextWorks, make the desired change to the INMAGIC.INI file, then restart DB/TextWorks and export the page.

    AutoIncludeValidationLinks=On edit forms, controls whether the box labels for fields with validation lists are turned into hypertext links which display the validation list. 0 = All fields with validation lists have validation list links (default)
    1 = Only fields with Validation specified in "Web box treatment:" on the Box Properties>HTML tab in the Form Designer have validation list links.
    BoxHighlighting=Controls whether the current box on Web query/edit forms has a selection box. 0 = Selection box displayed (default)
    1 = No selection box
    WebLinkINM=Specify the appearance of the Inmagic attribution line at the bottom of Web pages:

    0=Default appearance using logo and hypertext link:
    Powered by DB/Text WebPublisher, from [INMAGIC logo GIF]

    1=Change the logo/link to plain text:
    Powered by DB/Text WebPublisher, from Inmagic, Inc. (www.inmagic.com)

    WebHideINM=1Completely remove the attribution line and the accompanying horizontal rule


    Troubleshooting

    The DB/TextWorks Messages textbase (DBTMSG) is also a good source for troubleshooting information.

    Troubleshooting - General

    Inmagic recommends using the latest version available to you. Free service packs for Inmagic Products are available from the Customer Extranet.

    If you are using Windows 95 or 98 and you get an "application error" whenever you display information from any textbase, try using the V4Repair=1 line described in the "INMAGIC.INI Entries" section.

    The video driver you are using may cause display anomalies. If you see a display anomaly (e.g., text not being refreshed), try the same behavior using the Windows standard VGA or SuperVGA driver. If it doesn't happen with these standard drivers, there may be a bug in your video driver. Contact the vendor for a later version or use the VGA or SuperVGA driver.

    Troubleshooting - Printers

    Some printer settings may cause printing anomalies. Examples:

    Font Substitution

    If the Report Printing form includes borders, highlighted search items near the borders may cause parts of the border not to appear.

    Use the Windows Control Panel to change the Print Setup for this printer. Choose Options and then Fonts (or sometimes Advanced). If there is a section on True Type Fonts, you may need to select 'Use Printer Fonts for All TrueType Fonts', or edit the font substitution table to use 'Download as Soft Font' for the text font used in your form.

    True Type Fonts

    If your Report Printing form uses TrueType fonts, you may see a MEM OVERFLOW error on the printer's display panel when printing long reports (more than around 30 pages).

    The solution is to do one or more of the following:

      Home page | Inmagic software | Crew-Noble services | Training Dates  
      About Crew-Noble | What's new? | Contact us  

    Crew-Noble Information Services
    323 El Pintado Heights Drive, Danville, CA 94526-1412
    Phone: (925) 837-1399   Fax: (925) 820-9114

    Revised: 10/03/05