Inmagic® DB/TextWorks® and
Inmagic® DB/Text® WebPublisher PRO
Version 8.00 README File


Copyright © 1995–2004 Inmagic, Inc. All rights reserved. 

This README file covers Inmagic® DB/TextWorks® and Inmagic® DB/Text® WebPublisher PRO. You only need to read about those products that you purchased.

Contents

About the Products

What's New in this Version?

Converting Annotations for Use in DB/TextWorks 8.00

Issues Resolved

Backward Compatibility Issues

Compatibility Information for Windows 2000

Troubleshooting

Documentation Resources

Contacting Inmagic, Inc. and Communicating with Others


About the Products

DB/TextWorks is a content management system—a type of database software that enables you to build networked and standalone textbases to manage text, numbers, dates, and electronic images. DB/TextWorks combines traditional database power, including the ability to manipulate data and perform arithmetic calculations, with the ability to handle large amounts of text. When you want to publish your textbase(s) over the Web, you need to use DB/Text WebPublisher PRO.

DB/TextWorks also provides you with access to Inmagic.net™, which gives you the ability to connect to the Inmagic server from within a DB/TextWorks session to accomplish various tasks related to cataloging, indexing, and disseminating information throughout an organization.

DB/Text WebPublisher PRO is a server version of DB/TextWorks that enables you to publish textbases on the Internet or an intranet, so Web users can search them. WebPublisher PRO accepts queries from standard Web browsers, such as Microsoft Internet Explorer, and accepts XML function calls. The software returns search results in dynamically generated HTML and XML reports, and allows for editing over the Web. WebPublisher PRO, which is a separate product to be purchased, is used together with DB/TextWorks, which is the "buildware" for creating searchable textbases.


What's New in this Version?

This section lists each new and enhanced feature for DB/TextWorks and WebPublisher PRO. Where applicable, you are directed to other documentation for more information.

DB/TextWorks

  • Dead URL Link Checker. This new feature (available on the Tools menu after you open a textbase) gives you the ability to check the status of a URL link recorded in a textbase. Status information about the URL link (for example, whether it is live, live but with errors reported, or dead) is written to another field you designate in the same textbase. From the information provided after running the Dead URL Link Checker, you may find the need to make corrections to URL addresses or you may decide to delete addresses that no longer work. For more information, see the online help.
     
  • DB/TextWorks 8.00 uses a different image annotation library than earlier versions. Any existing annotations will not be visible in image windows until you use the DBTANNCONV.EXE program to convert the annotations for each textbase. This program resides in the DB/TextWorks installation folder. Annotations now have a .ANN extension by default. Note the following differences:
     
    • There are three new annotation objects: Filled Rectangle, Filled Ellipse, and Filled Polygon.
       
    • The ability to apply a fill pattern to an object is not available.
       
    • The way polylines are created has changed. With version 8.00, create a polyline by using the Polygon object and not connecting the end point with the starting point, thus leaving the polygon open as a polyline. (Note that if you end the object within 3 pixels of the starting point, the polygon will be automatically connected.) Because of this, the Polyline object does not appear in the Annotations toolbox or on the Annotations menu.
       
    • Sound annotations are no longer available.
       
    • The background color specified on the Annotation Properties dialog box (choose Annotations>Annotation Properties) affects the background of sticky note objects and text objects (while in edit mode) only. Line objects (that is, lines, arrows, and unfilled rectangles, ellipses, and polygons) with a line style other than solid may have a background color applied (applied in earlier versions of DB/TextWorks) when viewed. However, you cannot change the background color of these line objects.
       
    • You cannot specify a border for annotation objects.
       
    • The foreground color specified on the Annotation Properties dialog box (choose Annotations>Annotation Properties) is the color used to fill an object, for line color, and for text color. Because of this, the Color drop-down list on the Font dialog box (choose Annotations>Annotation Properties, then click the Set Font button) is not needed and has been removed.
       
    • The Strikeout and Underline options on the Font dialog box (choose Annotations>Annotation Properties, then click the Set Font button) are not available.
       
    • There is only one type of arrowhead.
       
    • Cut, Copy, Paste, and Undo are no longer available.
       
  • About this Computer System. This new command on the Help menu displays various information about the current computer system and user login properties.
     
  • Get Data. The Get Data command on the Inmagic.net menu has been removed. Inmagic, Inc. no longer supports the ability to download bibliographic data for information resources purchased through Inmagic.net.
     
  • New toolbar button appearance. Starting with this release, toolbar buttons in DB/TextWorks have a flat appearance. When a user moves the mouse pointer over a button, its appearance becomes three-dimensional.
     
  • Long file names. DB/TextWorks now stores long file names internally for menu screens, link definitions, and image annotation lists. Previous versions stored the short file name.
     
  • Improved viewing of the textbase log file. When you view the log file for a textbase (choose Maintain>View Log File), you can now search for information in the "up" direction. Previously, choosing Edit>Find only searched the log file in the "down" direction.
     
  • Master Password Required dialog box is now wider.
     
  • Recover Textbase command no longer truncates the name of the new, recovered textbase. Instead, the full name of the textbase is preserved and a counter (for example, the number "1") is appended to it.
     
  • For scripting, FormatFlagXML is now available for the ImportDescriptor and ExportDescriptor script objects. For more information, see the DB/TextWorks online help.
     
  • Bar Code Generation application now available. This application is for new customers as well as those on maintenance who have not received this application. The BarCodes textbase and Bar Code Generation query screen let you create bar code numbers. Use the Bar Code Generation query screen to specify a starting bar code number and the quantity of new numbers you want to generate, print bar code labels, and mark bar code numbers as printed. For more information, see the documentation provided with the application. To download the Bar Code Generation application, go to http://support.inmagic.com/downloads, select DB/TextWorks from the drop-down list and enter your serial number and password (which should have been supplied to you when you received your DB/TextWorks product), then click the Submit button. Click the Download Bar Code Application link and open or save the .EXE file that contains the BarCodes textbase and instructions.
     
  • Improved online help and README files. The information provided about the settings for the INI files used by DB/TextWorks and WebPublisher PRO has been moved from the README file to the DB/TextWorks online help. Along with other improvements to the README file, this file is now slimmer and more easy to read. The README file (README.HTM) is now for both DB/TextWorks and WebPublisher PRO. Previously, there were separate README files.
     

WebPublisher PRO


Issues Resolved

Version 8.00 addressed the following issues, listed by product. The applicable Inmagic tracking number follows each item listed, when available.

DB/TextWorks

  • Improved Thumbnail functionality. Previously, if you chose Images>Thumbnail and the image(s) had no image annotations, the "There is a problem processing the image annotation "." error message would display. This no longer happens. [8582]
     
  • Improved Image Annotation functionality:
     
    • The Annotation Properties dialog box now retains changes to the Line style drop-down list. [8385]
       
    • The scroll bars in the Images and Image Annotation windows now take annotations off the bottom or right edge of the image into account. If you add new annotation objects off the bottom or right edge of the window, the scroll bars and the Fit to Window function now take the new objects into account. [845, 8434]
       
    • If you choose Print when the Image Annotation window is active, you are prompted to save any unsaved changes first. Earlier versions simply printed the previous version of the annotation, if any. [8518]
       
    • In the Image Annotation window, if you add new annotation objects off the bottom or right edge of the window, the scroll bars and the Fit to Window function now take the new objects into account. [845]
       
    • The Image Annotation list now supports entries up to 250 characters. Previously, the Image Annotation list truncated entries as they approached approximately 100 characters in length. [888]
       
    • The image annotations count on the Manage Image Annotations dialog box is now accurate. Previously, the count used an estimate, so sometimes it was larger than the actual number of annotations. [1036]
       
  • Improved Textbase Log File functionality:
     
    • The message for the textbase log file for records that violate Require Strictly Correct Type on Link fields no longer displays the desktop-only "Do you want to browse the link terms list?" question. [8005]
       
    • Messages for the textbase log file now show the correct identifying field contents for records that were not changed because they were locked by another user or write-protected by record level security. Previous versions showed the identifying field contents for the last successfully-modified record. [8635]
       
    • Selecting identifying fields now works correctly on the Textbase Log File dialog box in Edit Textbase Structure function. [8446]
       
    • The textbase log file now records the login name and machine name of the individual who modified the structure through the Edit Textbase Structure function. [8639]
       
  • Print Definition for a query screen now includes the location of the Web navigational controls (Next/Previous buttons, and so forth). [8439]
     
  • Printed menu screen definitions now have a blank line between the header information (form name, and so forth) and the first box, for improved readability. [8451]
     
  • Creating a new textbase using the Copy an Existing Inmagic Textbase Structure option button could result in an empty validation list if the first entry in a validation list in the source textbase consisted simply of a carriage return. The only way to get an entry like this into a validation list is to use Accept & Update List on the Content Validation Mismatch dialog box. [8536]
     
  • The Deskew function now affects the Print Current Image option. Note that since the Deskew function only applies to the current image, it does not affect the Print Images in Current Record or the Print Images in Current Set option on the Select Images to Print dialog box. [8575]
     
  • The following problem does not happen now: If a report form included script buttons that were not anchored to a normal form box, when you used the mouse scroll wheel to scroll down in the report, the report appeared blank after the first record. [8585]
     
  • New SNBD12DM.DLL file from Snowbound Corporation corrects problem with SNBD11DM.DLL. Prior to this fix, for some JPEG images, Show Record Images would display white or black bars across the image. [8704]
     
  • DB/TextWorks no longer crashes in the following situations:
     
    • If you use the Print Reports for Refreshed Sets check box on the Refresh Sets dialog box. DB/TextWorks now displays the Print dialog box. [8736]
       
    • If you select Print Preview when no textbase is open and no menu screen is selected. [8745]
       
    • When you click the Print button on the Command Query window. [106]
       
    • When you interrupt a sort. DB/TextWorks now also does not exit when you interrupt a sort. [125]
       
    • When you copy and paste a very large text file into a field. [977]
       
  • DB/TextWorks XML Import now supports field names beginning with a digit or hyphen. Previously, it would either crash or display an error depending on whether the field was included in the XML import file. [114]
     
  • If you attempt to save an image annotation file whose name exceeds 127 characters, you receive a message indicating the problem is the length of the file name. The limitation is in the third-party Snowbound Image Annotation library. Previous versions displayed only the "There is a problem processing the image (error code 5362396)." message. [326]
     
  • The "You must add at least one field to the "Fields to be Exported" list." message now appears when appropriate. In the following situation, the message no longer appears: On the Fields to Export tab of the Export Options dialog box, if you selected the Export Subset of Fields option button then selected the Export All Fields option button again. [332]
     
  • The Edit Substitution List dialog box now detects and prohibits duplicate codes (the text before the colon). Previous versions would allow you to add, for example, both QA:Software Testing and QA:Quality Assurance. [763]
     
  • Customize Toolbar function now has a "How to Use Help" button. The "How to Use Help" button was inadvertently omitted in previous versions. [843]
     
  • The Print and Export options on the Manage Textbase Elements dialog box and the Print Definition option in the Form Designer now include the "starting page number" setting. [1052, 1060]
     

WebPublisher PRO

  • If you paste a term from a validation list and click the Submit Record button, then get an error message, when you click OK on the message page, the WebPublisher PRO edit page now shows your changes. Previously, the edit page did not include your changes. [8449]
     
  • Problems with insufficient rights to the QSETS directory now display a message. In previous releases, they could cut off the top of the report. [8471]
     
  • Width information is no longer included in <div> statements for box labels. This resolves an issue with some box labels that would wrap onto a second line. [8482]
     
  • XML input, AC=update with matchFound=deleteRecord now prevents deletion if the specified password does not provide Full access to all fields. [8484]
     
  • WebPublisher PRO now supports the "inm" namespace in XML input. For example:

  • <?xml version="1.0" ?>
    <inm:Query xmlns:inm="http://www.inmagic.com/webpublisher/query">
    <inm:QY>findall</inm:QY>
    <inm:AC>query</inm:AC>
    <inm:TN>cars</inm:TN>
    </inm:Query>


    [8495]
     
  • With SOAPFormat=1, searches that return no records no longer return an error; they return an empty record set. [8496]
     
  • The Back (<), Rewind (<<), and Close buttons now appear on report and expanded display pages when appropriate. Previously, these buttons sometimes did not appear if the form drop-down list was not shown. [8497]
     
  • Fixed Text content items treated as Raw HTML and containing more than 20 lines now work as expected. Previously, the box content was truncated at 20 lines and was not treated as Raw HTML. [8502]
     
  • For XML output, the text inside the [CDATA] tag no longer encodes XML-significant characters (for example, ampersand), except in the BU= parameter. [8505]
     
  • The Submit Record and/or Delete buttons now reliably appear if the edit form drop-down list is not shown on new record/delete record pages. Previously, the buttons would not appear on the new record/delete record pages in certain circumstances. [8533]
     
  • Clicking the Reset button caused a runtime error on edit forms created using Export Editing Form to HTML. Forms will need to be re-exported with DB/TextWorks 8.00 to correct the problem. [8539]
     
  • "Unknown field name" no longer appears when you use a validation list link or save a record using a Web edit form created using Export Editing Form to HTML, if the DBTWPUB.INI file contains SOAPFieldNameFormat=1 (now SOAPFormat=1) and a field name contains a space or hyphen or begins with a digit. For more information, see the DB/TextWorks online help. [8579]
     
  • The "Unknown field name" error message no longer appears on a WebPublisher PRO edit screen when you click the Submit Record button if any field name contains 20 characters and begins with a digit. [8586]
     
  • Different fonts for different content items now work in WebPublisher PRO. In version 7.0, the font class for the first content item was improperly being applied to the entire box. [8587]
     
  • Word Wheels now work reliably for query screens created using the Export Query Screen to HTML command. Previously, exporting to a file name containing a space, and possibly other factors, caused Word Wheels not to work. [8604]
     
  • New Record links on query screens created using Export Query Screen to HTML now work reliably. Previously, query screen file names containing a space, and possibly other factors, would cause New Record links to display a Runtime error. [8605]
     
  • The "No query criteria specified." pop-up message behaves properly for Web query screens. Previously, exporting to a query screen file name containing a space, and possibly other factors, would prevent the message from appearing when appropriate. [8606]
     
  • The current version displays the "Insufficient server resources to process your request—field data in record too large (<number of bytes> bytes)." message if a single entry exceeds 128K characters. Previously, WebPublisher PRO edit screens displayed the "The disk is full" Runtime error message or other errors when you clicked the Submit Record (or the Delete button) if the record contained extremely large field contents (for example, greater than 100,000 characters). [8618]
     
  • The 1-pixel horizontal rule that appeared if you used WebHideINM=1 to hide the Inmagic attribution line has been replaced with a 0-pixel horizontal rule so that it is not visible. [8622]
     
  • The "You cannot delete records because your password does not have full access to all fields in the textbase. At least one field is protected (hidden or read-only)." message now only appears when appropriate. Previously, it appeared after you tried to delete a record if the textbase contained any <Deleted> field, regardless of whether the textbase had passwords or whether you were using a password with Full access to all fields. At that time, you had to rename the <Deleted> fields in order to delete records on the Web. [8624]
     
  • The Inmagic Choices Browser used on Web edit pages is now compatible with SSL (https:) access. Previously, an error concerning the ICHOICES.XSL file was displayed. [8655]
     
  • The ASP page used by WebPublisher PRO edit/delete pages now supports HTTPS access. [8656]
     
  • The diagnostics page now returns the contents of any message INI file (MessageFile=filename.ini) as plain text. Previous versions returned them as HTML so that you had to use the View Source command in the browser to see the actual text. [8661]
     
  • The diagnostics page now includes HTTP server and System information. It also includes information on each textbase file and whether it exists and is read-only.

  • Note: The presence of [not found] after a file with the .ACS extension should not concern you unless the textbase has record-level security. [8668]
     
  • Word Wheel scroll bars now scroll to show the last entry in the list. Previously, sometimes they would not. [8723]
     
  • WebPublisher PRO now supports \r (carriage return) in XML input when using CGI. Previously, only \n (linefeed) was supported; \r or \r\n would cause the software to hang. [273]
     
  • Clicking the Submit Record button on a Web Edit screen (or the Delete button on a Web Delete screen) no longer causes the "Error: XML document must have a top level element." message to appear if IIS is set to use Integrated Windows Authentication. [370]
     
  • If IIS is using Basic Authentication, attempting to use a validation list link in WebPublisher PRO no longer returns an error about the ICHOICES.XSL file. To address the issue, ICHOICES.XSL is compiled into the DBTWPUB.DLL file and is no longer a separate file in the XSL directory. [421]
     
  • If the Web Edit form has no box for an XML match field, and that field has repeating entries in a record, WebPublisher PRO uses only the first entry in the field for matching purposes. In this case, all entries are used if the XML match field does appear on the edit form. If you see the "Found multiple records in textbase that match the record in the incoming data." message when the field contents (but not individual entries) in the XML match field are unique, add a box for the XML match field to the Web edit form. Previous releases displayed the "Error loading XML stream - An invalid character was found in text content." message. [557]
     
  • An omitted message was added to the WebPublisher PRO WPENGMSG.INI file. The message is: "The DB/Text WebPublisher Multiple Textbase Query screen has been renamed or deleted. Please contact the webmaster for this site." [684]
     
  • WebPublisher PRO now returns "Unable to access the textbase." in the following situations:
     
    • If the textbase is busy because someone is using the Batch Delete command in DB/TextWorks. The previous version returned a "DB/Text WebPublisher internal error..." message. [794]
       
    • If the textbase files are damaged. Previously, certain types of damage would cause a blank page to be returned. [863]
       
  • If WebPublisher PRO expanded display pages open in a separate browser instance (because you are using WebExpandInSeparate=1 or ES=1), the Close button always appears by default. Previously, Close only appeared by default for WebExpandInSeparate=1. [906]
     
  • WebPublisher PRO is now compatible with the MSXML4 SP2 DLLs, and these files are installed with all Inmagic products (DB/TextWorks, WebPublisher PRO, and PowerPack). [997]

Converting Annotations for Use in DB/TextWorks 8.00

Run the Inmagic Annotation Converter application (DBTANNCONV.EXE), which was installed with DB/TextWorks version 8.00, for each DB/TextWorks textbase that contains image annotations that you want to use in version 8.00.

To run the conversion program, you must have exclusive access to the textbase.

  1. Start the Inmagic Annotation Converter application (double-click DBTANNCONV.EXE, located in the DB/TextWorks installation folder).
     
  2. Choose Convert Image Annotations>Convert Annotations in Textbase to open the Select Inmagic DB/TextWorks Textbase dialog box.
     
  3. Select the textbase containing the image annotations you want to convert, then click Open. If the textbase has passwords, you are prompted for the Master password.
     
  4. A message appears showing the number of image annotations in the textbase and explains that the old format will be converted to the new format. Click Yes to proceed with the conversion.
     
  5. Another message appears listing the number of annotations converted, skipped, and/or not converted. Click OK to dismiss it.
     
  6. Close the Inmagic Annotation Converter application.

To verify that the annotations have been converted, open the textbase in DB/TextWorks version 8.00 and search for one or more records that you know have image annotations. Display the images and see if the annotations appear.

Note: As of DB/TextWorks version 8.00, the annotation files have the default extension of .ANN. Previously, annotation files had the default extension of .ART.


Backward Compatibility Issues

Note that Inmagic® DB/Text® ODBC Driver version 7.01 and DB/TextWorks version 8.00 are compatible only under limited circumstances. The following outlines the compatibility requirements for clients running ODBC version 7.01, WebPublisher PRO version 7.01 and earlier, and the Run-time version software (which is a standalone, search-only version of DB/TextWorks).

  • Can be used with DB/TextWorks 8.00 if:
    • The textbase structure is not modified.
       
    • The public textbase elements (query screens, forms, and record skeletons) or textbase default elements are not changed. Note that public saved sets can be changed (for example, refreshed, or created) without affecting backward compatibility.
  • Cannot be used with DB/TextWorks 8.00 if:
    • The textbase was created using DB/TextWorks 8.00.
       
    • The textbase structure was modified using DB/TextWorks 8.00.
       
    • Any public textbase element (query screen, form, or record skeleton) or the textbase default elements were modified using DB/TextWorks 8.00.

Compatibility Information for 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, see http://support.microsoft.com/default.aspx?scid=kb;EN-US;q307982.


Troubleshooting

This section contains the following topics:

Critical Errors

All DB/TextWorks messages are documented in the DB/TextWorks Messages textbase (DBTMSG) included in the Inmagic Applications group (click the Windows Start button, then click Programs>Inmagic Applications>DBTextWorks>Messages Textbase). However, there are several messages that 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.

Error message: "Cannot create directory '<directory>'."

Reasons:

  • This is the first time you have run DB/TextWorks or your UserFilePath setting has been removed from the Windows Registry.
     
  • You typed a directory that does not already exist in the User File Path dialog box, 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 click OK, you will return to the User File Path dialog box so you can try again.

Solution: Verify that:

  • You typed a path (that is, a drive and directory), not a file name.
     
  • The drive you specified, if any, exists (and if you are on a network, that you are connected to it or logged in).
     
  • You have the necessary rights to create a directory on that drive.
     
  • The directory name is a valid directory name.
     
  • If you typed multiple directory levels, all directories above the specified directory already exist (for example, if you typed C:\User\Temp\DBTEXT, verify that C:\User\Temp already exists).
     
  • No file exists with the directory name you specified.

Try creating the directory manually by choosing File>New>Folder in Windows Explorer.

If all else fails, accept the default that DB/TextWorks supplies (for example, C:\Program Files\Inmagic\).

Error Message: Cannot open license file. Contact system administrator.

Reason/Solution: 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. Have someone with Write and Create access to the directory containing the software run DB/TextWorks. The license file will be created automatically.

Error message: Cannot read 'dbtext32.cmx'

Reasons/Solutions:

  • The DBTEXT32.CMX file is missing or damaged. If the DBTEXT32.CMX file is missing or damaged, re-install DB/TextWorks.
     

  • OR
     
  • You pressed OK on the Enable or Upgrade Network dialog box when you do not have Write access to the directory where the DBTEXT32.CMX file is located. To get to this dialog box, you choose Tools>Enable or Upgrade Network. When you press Cancel on the Enable or Upgrade Network dialog box, you will receive an "Error opening file DBTEXT32.CMX: Access denied." message. Log in using a user ID that has Full access to the directory where DB/TextWorks is installed before attempting to increase the number of licensed users. Note that if the DBTEXT32.CMX file is write-protected, you get an error message when you select the Enable or Upgrade Network command and click OK.

Error message: Directory does not exist. Create it?

Reasons/Solutions:

  • This is the first time you have run DB/TextWorks or you have deleted your UserFilePath setting in the Windows Registry or INMAGIC.INI file (for example, by renaming or the file). If this is the first time you have run DB/TextWorks and you want to create the new directory, click Yes.
     

  • OR
     
  • You typed a directory that does not already exist in the User File Path dialog box. If you already have existing user files, or you made a mistake when typing the directory name, click No. You return to the User File Path dialog so you can specify the directory where your user files (extension .TBU) are already located.

Error message: File 'd:\path\tbname.dbs' cannot be read by the software.

Reason/Solution: You attempted to open a version 8.00 textbase with an earlier version of DB/TextWorks. Open a version 8.00 textbase with DB/TextWorks version 8.00.

Error message: 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.

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

  • You clicked on a textbase box in a menu screen.
     
  • You chose one of the "last-used" textbases from the bottom of the File menu.
     
  • You chose File>Open.
     
  • You used one of the options on the Manage Textbases menu.
     
DB/TextWorks cannot find the file name shown in the message.

Solutions:

  • If you used one of the first two methods, the problem may be that you have moved or renamed the textbase or you are not connected to the network drive where the textbase is located. Or, the textbase may have been a temporary textbase that you have deleted because you no longer need it.
     
  • If you used one of the last two methods, the problem is probably more serious. The .TBA file exists, but other files are missing. The Recover Textbase command 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, and .ACF. If not, your only recourse is to restore the textbase from a healthy backup.
     

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

Reason/Solution: DB/TextWorks checks for several files on startup, including DBTEXT32.CMX and certain DLL files. The file name shown in the message is missing. Re-install 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.

Error message: Software has an invalid serial number. Please reinstall.

Reason/Solution: 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. Re-install DB/TextWorks from the original disks using the Setup program, and apply all subsequent patches (if appropriate).

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

Reason/Solution: You are running DB/TextWorks from write-protected media (for example, 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. Shell to DOS and type SET TEMP=C:\ or some other directory to which you have full access.

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

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

  • The textbase default indexing mode for this textbase is Immediate (exclusive access).
     
  • The other person used File>Change Indexing Mode to switch to Immediate (exclusive access).
     
  • The other person used one of the options on the Manage Textbases menu (for example, Dump Textbase, Load New Textbase, or Check Textbase). All of these options require exclusive access to the textbase.
     
  • Someone else is editing the textbase structure.

Solution: Wait until the other person finishes using the textbase. If this message appears frequently, you may want to do the following:

  • If the textbase default indexing mode is set to Immediate (exclusive access), change it. Choose File>Change Indexing Mode, select the Shared Immediate (multiple users) or Deferred option button, and select the Use as Textbase Default Indexing Mode check box. Note that this option is only available when you are using the Master password.
     
  • If users are switching to Immediate indexing, add or change any passwords in use so that they cannot. Clear the Exclusive (Immediate) Access Permitted check box for each password.
     
  • If "unauthorized" people are using the options on the Manage Textbases menu, add a Master password. You must know the Master password to use any of these options. You can enable a Silent password to provide default permissions to the textbase.

Error message: The user file path '<path>' specified in your user options does not exist.

Reason/Solution: 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. When you click OK on the message, the User File Path dialog will appear, with the user file path specified in your Registry filled in. If you'd like to create the user file path shown, click OK. Otherwise, specify a different user file path. For example, your Registry key may have been created by your network administrator and copied to everyone's machine. If you know where your user files are located, specify that directory. User files have the extension .TBU.

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

Reason/Solution: 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. You will be able to use Inmagic DB/TextWorks when someone else stops using it. If this message appears frequently, contact Inmagic Sales 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 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.

Error message: 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.

Reason/Solution: You attempted to run DB/TextWorks when Setup Workstation has not been run on this machine. Setup Workstation does not simply create shortcuts; it installs files and registry entries necessary for DB/TextWorks to run. 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.

Troubleshooting - General

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


Documentation Resources

The following resources are available for DB/TextWorks and WebPublisher PRO:

Resource Explanation
Inmagic DB/TextWorks Installation and Upgrade Notes This booklet, which comes with the product, explains how to install and upgrade the software. It is also available as a PDF file.
Inmagic DB/Text WebPublisher PRO Installation and Upgrade Notes This booklet, which comes with the product, explains how to install and upgrade the software. It is also available as a PDF file.
Inmagic DB/TextWorks User's Manual A user’s manual that covers DB/TextWorks and is available as a PDF file, which is included with the installation of the DB/TextWorks product.
Inmagic DB/Text WebPublisher PRO User's Manual A user’s manual that covers WebPublisher PRO and is available as a PDF file, which is included with the installation of the WebPublisher PRO product.
DB/TextWorks online help The help file, which covers DB/TextWorks and WebPublisher PRO, contains the most up-to-date information and includes more details than their user's manuals. To open the help file, start DB/TextWorks and press F1, or choose Help>Help Topics from the DB/TextWorks menu bar.
Inmagic Web Services Guide This guide describes the Web services - SOAP interface available for use with the DB/Text® product line. It is available as a PDF file, which is included with the installation of WebPublisher PRO and is also located on the Inmagic Technical Information page at http://www.inmagic.com/support.
Inmagic Web Products Schema Documentation This file contains information about each element you can submit in XML to WebPublisher PRO. It is located on the Inmagic Web site at http://www.inmagic.com/support.
Inmagic PowerPack Lite README File PowerPack Lite is bundled with DB/TextWorks, and you install PowerPack Lite from the same method as you installed DB/TextWorks (from an installation CD-ROM or from a download). ReadmePP.HTM was installed in the PowerPack Lite installation folder. It tells you what is new with this version; lists issues resolved from the previous release and any late breaking information; and contains other important information.
Knowledgebase and Web site Provides information via the Web. With DB/TextWorks open and a Web browser available:
  • To search for solutions to common problems, choose Help>Inmagic on the Web>Knowledgebase to go to the Inmagic Support Knowledgebase page.
     
  • To visit the Inmagic Web site, choose Help>Inmagic on the Web>Home Page or Help>Inmagic on the Web>Support Page.
HTML help pages for WebPublisher PRO These files provide help topics for WebPublisher PRO. See the online help for descriptions of WEB_BEGIN.HTM, WEB_ICHOICES.HTM, WEB_MSG.HTM, and WEB_WW.HTM, which are in the HELP subfolder of the WebPublisher PRO installation folder.


  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

Communicating with Other Users

You can communicate directly with other users by participating in one or more Inmagic Web forums. To do so, go to the Inmagic Web site (http://www.inmagic.com) and from the Support menu, click Forums.

1204