Inmagic® DB/Text® WebPublisher PRO
v7.0 README File

This document discusses INI file settings and various other WebPublisher issues that may not appear in the printed documention or online help. Throughout, "HTTP server machine" refers to the machine where WebPublisher is installed.

If you didn't choose to register online at the end of the installation, you can Register Online now.

WebPublisher users: This README discusses WebPublisher PRO features. WebPublisher is the read-only version of WebPublisher PRO, so any discussion of Web editing does not apply to WebPublisher.

WebPublisher Lite users: The "Textbase File Locations" section in "Chapter 8: For the Webmaster" of the Inmagic DB/Text WebPublisher PRO User's Manual does not apply to DB/Text WebPublisher Lite. WebPublisher Lite ignores the [WebPublisher Textbase Paths] section and the Default-Textbase-Paths= line. Instead, see the description of the [WebPubLite] section in DBTWPUB.INI. Since WebPublisher Lite permits you to search only a single textbase, WebPublisher Multiple Textbase Query is not available. The CARS textbase for the Tutorial in Chapter 9 is not included for the non-PRO version of WebPublisher Lite.

You can use the following resources to learn DB/Text WebPublisher PRO:

DB/Text WebPublisher PRO Technical NotesExplains how to use XML input with WebPublisher PRO.
DB/Text WebPublisher PRO SchemaSchema for XML input: http://support.inmagic.com/web.
DB/Text WebPublisher PRO TutorialXML tutorial using the CARS textbase
Inmagic DB/Text WebPublisher PRO Userís ManualHow to install and use WebPublisher PRO together with DB/TextWorks.
CARS textbaseA sample textbase so you can perform the tutorial in the WebPublisher PRO User's Manual.
Online helpHelp for DB/Text WebPublisher is integrated in the DB/TextWorks online help, to explain the many DB/TextWorks features that support WebPublisher. To access the help, start DB/TextWorks, press F1, and search for topics on DB/Text WebPublisher.
Knowledgebase and Web siteStart DB/TextWorks and choose Knowledgebase from the Help menu to go to the Product Support knowledgebase on the Web, where you can search for common problems and solutions. Or visit Inmagicís web site at http://www.inmagic.com
HTML help pages for clientsHTML pages to help clients who visit your Web site. These pages explain query methods: WEB_BEGIN.HTM, Word Wheels: WEB_WW.HTM, displaying & pasting from validation lists: WEB_ICHOICES.HTM, and error messages: WEB_MSG.HTM.
XML SchemaSchema for XML input: http://support.inmagic.com/web. Only the Query sections apply to WebPublisher. The rest refer DB/Text WebPublisher PRO

Note: If you have upgraded from a previous version of WebPublisher be sure to read DB/TextWorks & WebPublisher Compatibility Issues.

Contents


What's New in Version 7.0?

These are the new features and changes in WebPublisher 7.0:

What's New in Version 6.1?

These are the new features and changes in WebPublisher version 6.1:


What's New in Version 6.0?

There are several new features in WebPublisher version 6.0:


What's New in Version 5.2?

There are two new features in WebPublisher version 5.2:


What's New in Version 5.1?

There is one major new feature in WebPublisher version 5.1:

ADA Compliance - An optional DBTWPUB.INI setting permits you to specify that WebPublisher should use <NOSCRIPT> sections with links instead of buttons so pages are accessible to the visually impaired. A corresponding INMAGIC.INI setting controls how DB/TextWorks exports HTML query and menu screens.

The syntax of the WPENGMSG.INI file for the Message Translation feature has changed slightly. If you use the Message Translation feature and your message INI file includes the lines for the Next & Previous buttons, either delete those lines or modify them so they match the new syntax in the new WPENGMSG.INI file.


What's New in Version 5.0?

There are several new features in version 5.0:


What's New in Version 4.2?

There is one major new feature in WebPublisher version 4.2:

WebPublisher Multiple Textbase Query -- the ability to search multiple textbases with a single query screen. See the DB/TextWorks online help topic of the same name for more information.


What's New in Version 4.1?

There are two major new features in version 4.1:

  • Improved Report/Display Formatting - Reports and expanded displays look more like they do in DB/TextWorks.
  • Multi-Lingual WebPublisher - The ability to translate messages and button text.

  • Creating the /DBTW-WPD/ Virtual Directory

    A /DBTW-WPD virtual directory is required in order for WebPublisher to function properly. This section explains briefly how to set up this virtual directory for various HTTP servers. For more information or if your HTTP server isn't listed, see the documentation and/or online help for your HTTP server.

    Microsoft Internet Information Server 5.0 (Windows 2000)

    1. Start the Internet Service Manager. For example, using the right mouse button, right-click the My Computer icon on your desktop. Select Manage from the menu that appears. Expand Services and Applications, then expand Internet Information Services.
    2. Right+click on "Default Web Site" and choose New>Virtual Directory from the menu.
    3. In the "Alias to be used to access this virtual directory" box type dbtw-wpd and press Next.
    4. On the next dialog, type the installation directory (e.g., c:\webpub\) and press Next.
    5. On the next dialog, select Read, Run Scripts and Execute, then click Next then Finish.

    Microsoft Internet Information Server 4.0

    1. Start the Internet Service Manager. For example, choose Programs>Microsoft NT 4.0 Option Pack>Microsoft Internet Information Server>Internet Service Manager.
    2. Right+click on "Default Web Site" and choose New>Virtual Directory from the menu.
    3. In the "Alias to be used to access this virtual directory" box type dbtw-wpd and press Next.
    4. On the next dialog, type the installation directory (e.g., c:\webpub\) and press Next.
    5. On the next dialog, check Allow Read Access, Allow Script Access and Allow Execute Access and press Finish.

    Microsoft Internet Information Server 4.0 - HTML

    The HTML interface is an alternative to the dialog interface described above.

    1. Start the Internet Service Manager (HTML). For example, choose Programs>Microsoft NT 4.0 Option Pack>Microsoft Internet Information Server>Internet Service Manager (HTML). It may be necessary to first start the Administration Web Server using the Internet Server Manager (non-HTML).
    2. Select "Default Web Site" and press the New link at the top left of the screen.
    3. Type dbtw-wpd in the pop-up dialog that appears.
    4. Select the dbtw-wpd choice in the list and press the Properties link on the left side of the page.
    5. In the Application section, select "Execute (and Scripts)" from the droplist.

    Microsoft Internet Information Server 3.0

    The "lite" version of Microsoft Internet Information Server is called "Microsoft Peer Web Services". Follow the procedure described below, but substitute "Microsoft Peer Web Services (Common)" in the first step.

    1. Start the Internet Services Manager. For example, choose Programs>Microsoft Internet Information Server (Common)>Internet Service Manager.
    2. Select the WWW service and start it if it is not already running.
    3. Choose Service Properties from the Properties menu.
    4. Choose the Directories tab and press the Add button.
    5. Type the installation directory (e.g., c:\webpub\) in the Directory box.
    6. Type /dbtw-wpd in the Virtual Directory Alias box.
    7. Check the Read and Execute boxes in the Access section.
    8. Press Apply then OK.

    Netscape Enterprise Server 3.5.1

    1. Start the Netscape Server Administration program. For example, choose Programs>Netscape SuiteSpot>Administration.
    2. Type the Netscape Administration username and password when prompted.
    3. Click on the button for your HTTP server, under "Servers supporting general administration".
    4. Click the Content Management button at the top of the page.
    5. Select "Additional Document Directories" from the list on the left.
    6. Type dbtw-wpd in the "URL prefix:" box.
    7. Type the installation directory (e.g., c:\webpub) in the "Map To Directory:" box.
    8. Press OK then "Save and Apply". Press OK on the message that confirms your changes have been made.
    9. Click the Programs button at the top of the page.
    10. Select "CGI Directory" from the list on the left.
    11. Type dbtw-wpd/exec in the "URL prefix:" box.
    12. Type the EXEC subdirectory under the installation directory (e.g., c:\webpub\exec\) in the "CGI directory:" box.
    13. Press OK then "Save and Apply". Press OK on the message that confirms your changes have been made.

    Note: Netscape Enterprise Server does not support ISAPI; you must use the CGI JavaScripts. See Switching between CGI and ISAPI JavaScripts.

    O'Reilly WebSite

    This information applies to version 1.1f through 2.3. The user interface for later versions of O'Reilly Website may be different. Version 1.1f was included on a demo CD available from Inmagic, Inc. for previous versions of WebPublisher.

    1. Start the O'Reilly WebSite Web Server. For example, double+click on Services in the Windows Control Panel, select Web Server from the list and press the Start button.
    2. Right+click on the O'Reilly WebSite icon on your toolbar and choose "Website server properties".
    3. Select the Mapping tab.
    4. Select Documents in the List Selector, type /dbtw-wpd in the Document URL Path box, and the installation directory (e.g., c:\webpub\) in the Directory box. Press Add then press Apply.
    5. Select Standard CGI in the List Selector, type /dbtw-wpd/exec in the Standard CGI URL Path box, and the EXEC subdirectory under the installation directory (e.g., c:\webpub\exec\) in the Directory box. Press Add then press Apply then OK.
    Note: O'Reilly WebSite does not support ISAPI; you must use the CGI JavaScripts. See Switching between CGI and ISAPI JavaScripts.


    Setting WebPublisher Access Rights

    The Internet user account must have the necessary access rights to several WebPublisher directories and files. See your HTTP server documentation for information about the Internet user account. See your Windows documentation for information about using Windows NT Explorer to set access rights. You may find it easiest to assign the following access rights for the Internet user account:

  • Read access to the full WebPublisher installation directory tree.
  • Read-Execute access to the WebPublisher EXEC subdirectory.
  • Read-Execute access to the Windows System directory (e.g., c:\winnt\system32\).
  • Full access to the QSETS subdirectory.
  • Read-Write access to the root of the WebPublisher installation directory, so WebPublisher can write to DBTWPUB.INI.
  • Read access to the textbase directories specified during installation or by editing DBTWPUB.INI.
  • Read access to the directories that correspond to the virtual directories specified for images and logos during installation or by editing DBTWPUB.INI.
  • Example - Internet Information Server

    The first step is to determine the name of the Internet User account, usually IUSR_<machine name>, e.g., IUSR_INMAGIC. For IIS 3.0, you'd start the Internet Services Manager, e.g., Programs>Microsoft Internet Information Server (Common)>Internet Service Manager, select the WWW service and start it if it is not already running, and choose Service Properties from the Properties menu. The Internet user account name appears in the Anonymous Logon section of the Services tab.

    All of the following operations use Windows NT Explorer (choose Start>Programs>Windows NT Explorer).

    To set permissions for the WebPublisher installation directory tree:

    1. Right+click on the installation directory (e.g., c:\webpub) and choose Properties from the pop-up menu.
    2. Select the Security tab and press the Permissions button.
    3. Select the IUSR_<machine> account in the Name list and Read in the "Type of Access:" list. Check the "Replace Permissions on Subdirectories" box. Press OK.

    To set permissions for the QSETS subdirectory (must be set after permissions for installation directory tree):

    1. Right+click on the QSETS subdirectory under the installation directory (e.g., c:\webpub\qsets) and choose Properties from the pop-up menu.
    2. Select the Security tab and press the Permissions button.
    3. Select the IUSR_<machine> account in the Name list and Full Control in the "Type of Access:" list. Press OK.

    To set permissions for DBTWPUB.INI (the procedure is similar for INMAGIC.INI and DBTEXT.INI, except that only Read access is required):

    1. Locate DBTWPUB.INI in the installation directory, right+click on it and choose Properties from the pop-up menu.
    2. Select the Security tab and press the Permissions button.
    3. Select the IUSR_<machine> account in the Name list and Full Control in the "Type of Access:" list. Press OK.

    Note that despite the fact that the IUSR_<machine> account is normally a member of the Guests group, you must set permissions explicitly for the IUSR_<machine> account.

    Netscape Enterprise Server and O'Reilly WebSite use the System account by default. Permissions are controlled using Access Control (or ACL) in the HTTP server properties. See your HTTP server documentation for more information.


    WebPublisher INI Files

    WebPublisher reads various settings from the following three INI files:

    DBTWPUB.INITextbase and image directory settings specific to WebPublisher
    INMAGIC.INIOptions which may be shared with Inmagic DB/TextWorks
    DBTEXT.INIDate settings shared with Inmagic DB/TextWorks

    Only the DBTWPUB.INI file is mandatory. WebPublisher looks for all three INI files in the root of the installation directory. If it does not find them there, it looks in the Windows directory on the HTTP server machine. The account used by the HTTP server needs read access to all three files if they exist. Write access is recommended but not required for DBTWPUB.INI.

    DBTWPUB.INI

    The DBTWPUB.INI file controls:

  • where WebPublisher looks for textbases and images used in reports and single-record displays
  • how many query sets are retained for each textbase
  • how report/display pages are formatted
  • whether WebPublisher messages are translated
  • The Internet user account must have read and write access to this file.

    Textbase Search Path

    When you installed WebPublisher, you had the opportunity to specify a textbase search path. You can also optionally indicate a specific location for each textbase. When a user presses the Submit Query button:
    1. WebPublisher checks the [WebPublisher Textbase Paths] section for the textbase name, and looks in the specified location.
    2. If the textbase name does not appear in the [WebPublisher Textbase Paths] section or isn't found in the specified location, WebPublisher looks in the directories specified in the Default-Textbase-Paths= line in the [WebPublisher Defaults] section.
    3. If the textbase isn't found in either location, WebPublisher displays a page giving the end user the option do a recursive subdirectory search on the directories listed in the Default-Textbase-Paths= line.
    4. If WebPublisher finds the textbase in either step 2 or step 3, it writes the location to the [WebPublisher Textbase Paths] section, so the search will not be necessary in the future.
    Example:

    [WebPublisher Defaults]
    Default-Textbase-Paths=c:\data\,c:\webpub\textbase\

    [WebPublisher Textbase Paths]
    cars=c:\webpub\sample\
    catalog=c:\data\library\

    The internet user account must have read rights to the directories where textbases are located. In order for the textbase search feature to work properly, this account must also have write access to DBTWPUB.INI and read access to all directories specified in the Default-Textbase-Paths= line.

    Textbase Location [WebPubLite]

    When you installed DB/Text WebPublisher Lite, you had the opportunity to specify the location of the textbase you want to use. If you didn't do so, or have moved or renamed the textbase, this is the format for the required [WebPubLite] section. In this example, the textbase is named CATALOG and is located in the c:\data\library\ directory.

    [WebPubLite]
    WebPubLite-Name=CATALOG
    WebPubLite-Path=C:\DATA\LIBRARY\

    The Internet user account must have read rights to the directory where the textbase is located.

    Image Locations for Reports & Single-Record Display

    You can specify the location where WebPublisher looks for:

  • Fixed images - logo and background images used in reports and single-record display
  • Record images - image file names specified in textbase records, included as inline images or image links
  • You can specify an image location for each textbase, and/or put images in a default location. WebPublisher removes any path information specified for the image in the textbase record, then constructs the image URL by pre-pending the text you specify. Use the [WebPublisher Logo Locations] section to specify the text WebPublisher should use to construct the URL for fixed images for specific textbases. Use the [WebPublisher Image Locations] section for record images. Use the Default-Logo-Location= and Default-Image-Location= lines in the [WebPublisher Defaults] section to specify the text used to construct the image URLs if the textbase name does not appear in either of the other sections.

    Example:

    [WebPublisher Defaults]
    Default-Textbase-Paths=c:\data\,c:\webpub\textbase\
    Default-Logo-Location=/images
    Default-Image-Location=/pictures

    [WebPublisher Image Locations]
    cars=/dbtw-wpd/sample/
    vacation=http://mydomain.org/me/photos/

    [WebPublisher Logo Locations]
    vacation=http://mydomain.org/me/logo/

    Note that the specified image locations must be accessible via HTTP, for example, as a virtual directory in your HTTP server properties.

    Maximum Query Sets

    Records returned by a DB/Text WebPublisher query are called a set. A set is generated for each successful query and each time a user changes the form. A set provides the Internet or intranet user with the ability to view successive subsets of the records retrieved without having to re-execute the query.

    Query sets are stored temporarily on the server in /dbtw-wpd/qsets, under automatically-generated hidden names. Two files track query sets: .WPD and .WPO. These files have the same name as the textbase. For example, a textbase called SALES uses SALES.WPD and SALES.WPO.

    You can specify the maximum number of sets to retain. When the maximum is reached, slots will be reused as needed, beginning with the oldest. The default value is 2000. Specifying less than this number may free up some disk space, but may cause sets to be reused (thus removed) before users are finished with them. This can result in users getting messages such as "Your current query has expired. Perform the search again" when they display records or change forms.

    To change the value, edit the WebSetMax parameter in the [WebPublisher] section of the DBTWPUB.INI file. This file is normally located in the WebPublisher installation directory on the HTTP server. (If you upgraded from an earlier version of WebPublisher, it may be in the Windows directory.)

    [WebPublisher]
    WebSetMax=2000

    Report/Display Formatting

    By default, WebPublisher version 4.1 uses Cascading Style Sheets (CSS) and absolute positioning, so report and display forms look as much as possible as they would look in DB/TextWorks.

    WebPublisher detects whether the browser supports Cascading Style Sheets. If not, WebPublisher uses simple HTML (boxes will be left-justified, box labels will appear on top rather than to the left, etc.). Netscape and Internet Explorer version 4.0 or later usually support Cascading Style Sheets.

    Forms which contain Raw HTML or Inline Images are incompatible with absolute positioning. Forms containing these elements will have overlapping text unless very carefully designed. Therefore, simple HTML is used for this type of form unless you explicitly set WebCSSOpt=2 in your DBTWPUB.INI file (see below). Note: DB/TextWorks tabular forms do not use absolute positioning, so this issue doesn't affect them.

    You can use picture boxes in place of inline images to retain CSS formatting. The "Image size" option specified using Box Properties>Position in the Form Designer is used. In order for the image sizing to work properly, the images must reside either in the textbase directory (e.g., c:\catalog\) or the directory specified in the Image field in the record (e.g., c:\images\coyote.jpg).

    To control whether the site uses CSS, modify the [WebPublisher] section of your DBTWPUB.INI file to include the following line:

    [WebPublisher]
    WebCSSOpt=1

    0 = don't use CSS
    1 = the default behavior
    2 = use CSS regardless of whether forms contain Raw HTML or inline images

    You can override the WebCSSOpt= setting for an individual query screen or menu screen by using the CS= parameter. For example, add a line like the following:

    <INPUT NAME="CS" TYPE="hidden" VALUE="2">

    Message Translation

    You can change the text of many of the messages and buttons that WebPublisher displays, either to translate them into another language or simply to make them clearer to your end-users.

    You have two options:

  • Use the same set of messages for all query and menu screens (read on)
  • Specify which set of messages to use with each query or menu screen (see Using Multiple Languages with WebPublisher)

    When you install WebPublisher, a WPENGMSG.INI file is installed in the root of the installation directory. This INI file includes the messages you can translate. We recommend leaving the original file intact and making a copy under a new name. Messages are limited to 250 characters, and must be all on one line. They can include HTML codes, and do for strings such as the button text on the Next Record button.

    A simple example (translating "No records found by latest query."):

    msg_110=<BR><BR><BR><CENTER><HR>Your search didn't find any records<BR>Please press your browser's Back button and try again.<HR></CENTER>

    If you also want to specify Word Wheel button text or change the "No query criteria specified." message, you need to modify this section of the message INI file:

    [Localized Query Parameters]
    qmNoQuery=No query criteria specified.
    wwButtonLabel=Word Wheel
    wwButtonWidth=120
    wwButtonHeight=35

    Normally, you won't need to modify the height. You'll only need to modify the width if the button text is cut off.

    Once you have made the desired changes, specify which message INI file to use in the [WebPublisher] section of your DBTWPUB.INI file:

    [WebPublisher]
    MessageFile=MYWPMSG.INI

    New Search button

    You can specify that every page should have a New Search button next to the Next/Previous buttons. When the user clicks the button, they'll return to the empty query screen (or to the menu screen). To make the button appear, add the WebNewSearchButton parameter to the [WebPublisher] section of the DBTWPUB.INI file.

    [WebPublisher]
    WebNewSearchButton=1

    Note: If you use the WebExpandInSeparate parameter described below, the New Search button will not appear on the expanded records because the button could not return them to the query screen in the original browser window. The New Search button will still appear on the multiple-record report pages.

    Expand Record in new window

    You can specify that when a user clicks an expand record link, the record will open in a new Web browser window. This makes it easy for the user to return to their report by closing the expanded record window. Add the WebExpandInSeparate parameter to the [WebPublisher] section of the DBTWPUB.INI file.

    [WebPublisher]
    WebExpandInSeparate=1

    You can override the WebExpandInSeparate parameter for an individual query or menu screen by using the ES parameter. For example, you could add a line like the following:

    <INPUT NAME="ES" TYPE="hidden" VALUE="0">

    ADA Compliance

    You can specify that WebPublisher should use <NOSCRIPT> sections with links instead of buttons, for options like Next Record, New Search, etc. to make the pages accessible to the visually impaired. Add the WebScriptButtonsOption parameter to the [WebPublisher] section of the DBTWPUB.INI file.

    [WebPublisher]
    WebScriptButtonsOption=2

    0 = always use buttons
    1 = always use links
    2 = both: buttons and <NOSCRIPT> section with links

    To create the corresponding HTML query screens and menu screens, exit all copies of DB/TextWorks, add the following line to the [Inmagic DB/TextWorks] section of the INMAGIC.INI file, and restart DB/TextWorks. Then export your menu screen or query screen to HTML.

    [Inmagic DB/TextWorks]
    ExportQBEtoHTMLOption=2

    0 = normal query/menu screen
    1 = no scripts
    2 = normal section and <NOSCRIPT> section

    Note: For HTML menu screens exported using option 1 or 2 above, you must manually add the BU= parameter to the HREF links in the page, if you intend to use the New Search button or images. Instructions for doing so are included as comments in the HTML source of the page.

    Total Records

    You can specify the total number of records WebPublisher will display. All of the records are sorted according to any compulsory form sort or textbase default sort before the set is truncated.

    There is no indication that the search retrieved more records than the TotalRecords value. For example, the RECORD COUNT variable and the browser title bar will display the TotalRecords setting.

    The records are still broken into multiple pages according to the "Records per page:" setting in the query screen.

    To set the total number of records displayed, add the TotalRecords parameter to the [WebPublisher] section of the DBTWPUB.INI file:

    [WebPublisher]
    TotalRecords=20

    You can use the TR= parameter in a query screen, menu screen or canned query to override any TotalRecords value specified in the DBTWPUB.INI file. For example:

    <INPUT NAME="TR" TYPE="hidden" VALUE="10">

    For XML output, use TotalRecordsforXML= in DBTWPUB.INI or TX= in the query screen instead. Note: TotalRecordsforXML= and TX= default to 1000 if neither is specified. To remove the limit on the number of records returned, use TotalRecordsforXML=0.

    Logging Internal Errors

    If you ever receive an internal error like the following:

    DB/Text WebPublisher internal error 0x2AF8. Please contact Inmagic, Inc.

    You can elect to also write these messages to a log file called WPTCERR.LOG in the QSETS directory. The messages will be date and time stamped.

    To do so, add EnableErrorLog=1 to the [WebPublisher] section of the DBTWPUB.INI file.

    Web Navigation, etc.

    Several enhancements have been made to the Web interface. Some of these can be disabled.

    Buttons

    The Next/Previous buttons always appear, even if you're on the first/last page of the report. To make the buttons disappear instead of begin disabled, add the following line to the [WebPublisher] section of the DBTWPUB.INI file:

    [WebPublisher]
    DisabledButtons=1

    Several other buttons appear on WebPublisher pages:

    To turn these off for the entire site, add the appropriate lines to the [WebPublisher] section of the DBTWPUB.INI file, as shown below. To turn them off for individual query pages, you can use a message INI file as discussed in Using Multiple Languages with WebPublisher.

    [WebPublisher]
    BackButton=0
    RewindButton=0
    CloseButton=0
    ErrorMsgButton=0

    Message Colors

    Error message pages automatically use the same background color as the page which generated the message. The text of an error message uses the same font as the box label for the first box on the form. If the first box is a text box, which cannot have a box label, black is used.

    To disable this feature for most pages, add the following lines to the [WebPublisher] section of your DBTPWUB.INI file. Note that this feature cannot be disabled for messages returned when you click Submit Record on an Edit page.

    [WebPublisher]
    BodyFgColor=0
    BodyBgColor=0

    INMAGIC.INI

    You can use the Options dialog in DB/TextWorks to select most of the desired settings, then copy the INMAGIC.INI file to the WebPublisher installation directory. If you're using the ISAPI JScript files, you must stop and restart the World Wide Web Publishing Service for WebPublisher to recognize changes made to the INMAGIC.INI file. See the DB/TextWorks online help for an explanation of the various Options. The italic settings listed below must be added using a text editor. These are the settings used by WebPublisher:

    [Inmagic DB/TextWorks] section
    Inclusive=Controls the Search preference 'Use inclusive search option for multiple fields':
    0 = Do not use inclusive search option
    1 = Use inclusive search option (default)
    IgnoreAccents=Controls the Search preference 'Ignore accents on extended characters':
    0 = Do not ignore accents when searching (default)
    1 = Ignore accents when searching
    NewData=Controls the Deferred Indexing preference 'Show deferred changes in reports and display':
    0 = Show old version of record (default)
    1 = Show record with deferred changes
    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
    * Recommended setting = 1 (so users can search for dates such as 12/31/98 and URLs such as http://www.inmagic.com without having to use surrounding quotes.)

    The [Highlight] section is slightly more complicated since WebPublisher behavior differs slightly from DB/TextWorks behavior.

    [Highlight] section
    Display=Controls the search highlighting behavior of the single-record display (expand record jump)
    1 = Bold (default) - reverse video in DB/TextWorks
    2 = Color, in this case a Color= line also appears
    Printing=Controls the search highlighting behavior of the multi-record display
    1 = Bold (default)
    2 = Italic
    3 = Bold Italic
    4 = Underline

    The [WebPublisher] section must be added manually. These options also affect edit, query and menu exported to HTML using Inmagic DB/TextWorks.

    [WebPublisher] section
    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 = Only fields with Validation specified in "Web box treatment:" on the Box Properties>HTML tab in the Form Designer have validation list links.
    1 = All fields with validation lists have validation list links (default)
    BoxHighlighting=Controls whether the current box on Web query/edit forms has a selection box. 0 = No selection box
    1 = Selection box displayed (default)
    WebLinkINM=0Specify 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
    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

    The easiest way to set the options in the [FormSettings] section is to set them using Tools>Options>Display>More Defaults>Colors in DB/TextWorks, exit DB/TextWorks, then copy the section from the DB/TextWorks INMAGIC.INI file to the WebPublisher INMAGIC.INI file.

    [FormSettings] section
    ApplyBkgOpt=Controls whether the form and box background colors are applied to forms with no explicit background color:
    1 = FormBkgColor is applied to saved forms with no explicit background color
    2 = FormBkgColor is ignored
    BoxBkgColor=Specifies the box background color for reports and expanded displays if no explicit color is specified in the form:
    Red,Green,Blue values separated by commas (e.g., 255,255,128 is yellow)
    FormBkgColor=Specifies the page background color for reports and expanded displays if no explicit color is specified in the form:
    Red,Green,Blue values separated by commas (e.g., 255,255,128 is yellow)

    DBTEXT.INI

    Use the options in the DBTEXT.INI file to control both the appearance of dates and how users can search for them. (See also the "SpacedRelOps=" option in the INMAGIC.INI file.) It is important that these settings match those used by DB/TextWorks. One way to ensure this is to copy the DBTEXT.INI file from the DB/TextWorks installation directory to the WebPublisher installation directory on the HTTP server machine. If you're using the ISAPI JScript files, you must stop and restart the World Wide Web Publishing Service for WebPublisher to recognize changes made to the DBTEXT.INI file. Most of these options can be set by using the DB/TextWorks Setup Configure option. The others must be added using a text editor.

    [Dates] section
    CenturyYear0=For 2-digit years, specifies the first year in the current century. For example, if you specify 1940, "96" means "1996" but "35" means "2035".

    [defaults] section
    dfltDays=List of primary day names that WebPublisher will recognize.
    These day names are also used when displaying formatted dates.
    Type seven day names in order, starting with Sunday, separated by spaces.
    dfltMonths=List of primary month names that WebPublisher will recognize.
    These month names are also used when displaying formatted dates. Abbrevations of these months are used when displaying date fields in the Word Wheel.
    Type 12 month names in order, starting with January, separated by spaces.
    dfltDays2=List of alternate day names that WebPublisher will recognize.
    dfltMonths2=List of alternate month names that WebPublisher will recognize.
    sShortDate=Specify short date format (e.g., dd/mm/yyyy). Can also affect searching (e.g., mm-dd-yy vs. dd-mm-yy)
    sLongDate=Specify long date format, primarily for displaying formatted dates (e.g., dddd, MMMM dd, yyyy)
    iDate=Specify order of date components (0=M-D-Y, 1=D-M-Y, 2=Y-M-D) for searching and date formatting.
    indexDateFmt=Controls the format of date indexes shown in the Word Wheel (default=YYYY-Mmm-DD).

    The sShortDate=, sLongDate= and iDate= lines are an alternative to making the Internet User account a member of the group Users so that it can read the System Regional settings (e.g., so that WebPublisher can recognize dates in dd/mm/yy format).

    [Advanced] section
    EnableSlotLog=1Have WebPublisher write a line to the textbase .SLT file every time it opens a textbase, and clear the line every time it closes a textbase. You can open the .SLT file with a text editor to see who has the textbase open. The account used by WebPublisher must have Full access to the .SLT file, which resides in the same directory as the textbase.


    Editing Records Using WebPublisher PRO

    You can edit, duplicate, and delete existing records using WebPublisher PRO. You can also add a New Record link to an HTML query screen. See the DB/TextWorks online help for more information about designing the appropriate forms and query/menu screens. Note that a New Record link on an Edit page performs a Duplicate Record operation.

    You should use Maintain>Edit Textbase Structure in DB/TextWorks to specify XML Match Fields before attempting to use the Web editing features. If you specify a single Match Field, it should either be an Automatic Number field, or have Unique Entries Only and Field Entry Required validation. Note that Match Fields are stored in the textbase .INI file, so be sure to copy this file if you copy the textbase.

    If a field has a validation list, by default the box label for that edit box will be underlined. If you click on the box label, a dialog box will display showing the field's validation list. You can paste entries from the list into the edit box.

    Notes:

    Web pages have several other features: highlighting the selected box, various navigation buttons, messages automatically using form colors, and so on. To turn these options off, see the [WebPublisher] section of the INMAGIC.INI section, and the Web Navigation, etc. section of the DBTWPUB.INI section.

    Using Multiple Languages with WebPublisher

    WebPublisher version 4.1 supports the ability to specify different sets of messages for different query or menu screens. You can also specify the text that appears on the Word Wheel buttons for that query screen.

    One common use for this feature is for bi-lingual (e.g., French/English) or multi-lingual sites. You can have several query screens, each for a different language.

    See Message Translation for information on formatting messages.

    You specify which message file to use by adding an MF= parameter to your query or menu screen.

    For menu screens, add the MF= variable to the dbtw_m_link() call. You must make this change after exporting the menu screen to HTML. Example:

    dbtw_m_link( "catalog", "myset", "RF=repform&DF=dispform&MR=15&DL=0&RL=1&NP=2&MF=mywpmsg.ini", "My Set" );

    For query screens, add a line like the following to the bottom of the page. If you add this line using a text box in the Query Screen Designer, be sure to treat the box contents as Raw HTML. You can also simply edit the query screen after exporting it to HTML to add this line.

    <INPUT NAME="MF" TYPE="hidden" VALUE="mywpmsg.ini">

    If you also want to specify Word Wheel button text for this query screen or change the "No query criteria specified." message, modify the dbtw_initialize() line in the exported HTML query screen file to specify the message file name. If you didn't export the query screen with version 4.1, you'll need to add the third parameter. If you did, you just need to type the message file name between the quotes. Example:

    dbtw_initialize("", "", "wpcarmsg.ini");

    Example: The CARSQMSG.HTM in the SAMPLE subdirectory of the WebPublisher installation directory (carsqmsg.htm) changes both the Word Wheel button text and the "No records found by latest query." message. Type "not there" in the first box and press Submit Query.


    Specifying that WebPublisher should return XML Output

    You can use the XM parameter to specify that WebPublisher should return record information in XML format. This feature permits you to have complete control over how WebPublisher output is formatted; no formatting is done by WebPublisher. For example, you could add this line to your HTML query screen to turn XML output on:

    <INPUT NAME="XM" TYPE="hidden" VALUE=1>

    Or you could add &XM=1 to a "canned" query.

    By default, WebPublisher will return the first 1000 the records found by the search as a single page, as <inm:Results>. You can change the limit on the number of records returned using TotalRecordsforXML= in the DBTWPUB.INI file, or TX= in the query screen. To remove the limit on the number of records, use TotalRecordsforXML=0.

    WebPublisher uses the report form (RF) specified to determine which fields to include. If no report form is specified, all non-hidden primary textbase fields are returned. If you want to include secondary textbase fields, you must specify a report form name. Fields that are on a form more than once are included only once. Field order on the form is not retained. First, all primary textbase fields are returned in textbase structure order. Then, all secondary fields are returned in the order in which they appear on the form.

    Records are sorted just as they are for normal WebPublisher output. If the specified report form has a compulsory sort, that sort is used. If not, the textbase default sort order, if any, is used.

    The WebPublisher program name and version are returned as attributes of <inm:Results>. The query string and any message (e.g., "No records found by latest query.") are also returned as part of the <inm:Results> in tag/value pairs. For example (the inm: appears before all tags):

    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
    <inm:Results productTitle="Inmagic DB/Text WebPublisher" productVersion="6.1" xmlns:inm="http://www.inmagic.com/webpublisher/query">
    <inm:Query>
    <![CDATA[ XC=%2Fdbtw-wpd%2Fexec%2Fdbtwpub.dll&BU=http%3A%2F%2Flocalhost%2Fdbtw-wpd%2Fsample%2Fcarsqxml.htm&QB0=AND&QF0=Type&QI0=kit+%26+assembled&QB1=AND&QF1=Name&QI1=&QB2=AND&QF2=Club+Price&QI2=&TN=Cars&DF=Images+and+Text&RF=Prices&DL=1&RL=1&NP=3&XM=1&AC=QBE_QUERY ]]> 
    </inm:Query>
    <inm:Error code="110" extra="">No records found by latest query.</inm:Error>
    <inm:Recordset AC="QBE_QUERY" setCount="0" />
    </inm:Results>
    
    When records are returned, the setCount= attribute shows how many records were found:

    <inm:Recordset AC="QUERY" setCount="30">

    Notes:

    Specifying an XML Style Sheet (XSL)

    To pass the name of an XML Style Sheet file (XSL) to WebPublisher, you use the XS= parameter. For example, you could add this line to your HTML query screen:

    <INPUT NAME="XS" TYPE="hidden" VALUE="/directory/yourfilenamehere.xsl">

    Notes:

    If you pass an XSL file name to WebPublisher, the "content" setting in the HTTP header information sent to the Web browser defaults to "text/html". You can use the DT (document-type) parameter to specify another value (e.g., "text/xml"). Note: The DT parameter can also be used to specify the document type for normal WebPublisher output, but it is primarily useful with XML output.

    WebPublisher Message Format (XE)

    If you don't specify an XSL file, WebPublisher messages (e.g., "Invalid password entered.") are returned in XML format.

    If you specify an XSL file, you can use the XE (XML Error) parameter specify in which format WebPublisher messages will be returned. For example:

    <INPUT NAME="XE" TYPE="hidden" VALUE="2">

    0 = HTML format (default)
    1 = XML format
    2 = transform the XML format using the specified XSL file

    Displaying XML Schema

    You can display the textbase schema or report form schema by changing the AC= value in the HTML query screen from QBE_QUERY to either TB_SCHEMA_QUERY (for the textbase) or RF_SCHEMA_QUERY (for the report form, RF=, specified in the query screen). For example:

    <INPUT NAME="AC" TYPE="hidden" VALUE="RF_SCHEMA_QUERY">

    If the textbase has passwords, both are affected by the password you specify. For RF_SCHEMA_QUERY, you must perform a search which retrieves records.

    Note: You must also set the XM parameter to 1 to display XML schema. If XM=0, then RF_SCHEMA_QUERY and TB_SCHEMA_QUERY will be treated as if you'd specified AC=QBE_QUERY.

    If you're using XML input, you can also use <AC>SCHEMA_INPUT</AC> and <AC>TB_SCHEMA_OUTPUT</AC>.

    Disabling XML

    You can disable XML (input & output) for all WebPublisher queries, or for an individual textbase.

    To disable all WebPublisher XML functionality, add the following line to the [WebPublisher Defaults] section of your DBTWPUB.INI file:

    [WebPublisher Defaults]
    Default-DisableXML-Setting=1

    To disable (or enable) XML for an individual textbase, add a [WebPublisher DisableXML] section to your DBTWPUB.INI file. Then add each textbase you want to control followed by =1 (XML disabled) or =0 (XML enabled). The setting in the [WebPublisher DisableXML] section overrides the setting specified using Default-DisableXML-Setting. In the following example, the you can use XML with the EMPLOYEES textbase:

    [WebPublisher DisableXML]
    catalog=1
    employees=0

    When XML is disabled, the end-user will receive one of these messages (in XML format, unless an XSL file is specified):

    The DB/Text WebPublisher XML feature has been disabled.
    The DB/Text WebPublisher XML feature has been disabled for this textbase.


    Using XML Input with WebPublisher

    Instead of a query or menu screen or canned query, you can use XML input to send commands to WebPublisher. The following example performs a search in the CARS textbase and displays the records using the Prices form in HTML format (XM=0):

    <?xml version="1.0" ?>
    <Query xmlns="http://www.inmagic.com/webpublisher/query">
    <AC>QUERY</AC>
    <TN>CARS</TN>
    <QY>Findall</QY>
    <RF>Prices</RF>
    <XM>0</XM>
    </Query>

    Notes:

    You have two options for specifying what fields are returned in the output:


    Specifying HTTP Header Information (content, expires)

    You can use the DT (document type) and XP (expires) parameters to specify the "content" and "expires" settings in the HTTP header information passed to the Web browser. The "expires" setting is in seconds. For example you could add these lines to your HTML query screen:

    <INPUT NAME="XP" TYPE="hidden" VALUE="120">
    <INPUT NAME="DT" TYPE="hidden" VALUE="text/html">

    DT is primarily useful with XML output, but can be used with normal WebPublisher reports in specific situations. If you specify an XML Style Sheet file (XS=) for XML output, DT is ignored for WebPublisher messages (e.g., "No records found by latest query."); use the XE parameter instead.

    XP may cause "Data Missing" errors when using Back, Print or View Source with some older versions of Netscape.


    Using Command Queries with WebPublisher

    You can use the QY parameter to specify WebPublisher search criteria in DB/TextWorks Command Query format. This feature permits users to do searches using fields which do not appear on the query screen, complicated nested Booleans, searches using set names, or other searches which are not possible using a query screen.

    You can use this option to make creating "canned queries" simpler, instead of including all the QB0/QF0/QI0 strings. Example:

    <A href="/dbtw-wpd/exec/dbtwpub.dll?XC=%2Fdbtw-wpd%2Fexec%2Fdbtwpub.dll&BU=http://domain/dbtw-wpd/sample/qysample.htm&QY=find+name+ct+ford&MR=10&TN=Cars&DF=Images+and+Text&RF=Prices&DL=1&RL=1&NP=3&AC=QBE_QUERY">QY Example</A>

    Or to permit your end-users to enter Command Queries via the Web. For example, you could replace the query boxes with the following:

    <B>Command Query:</B><BR>
    <INPUT TYPE="text" NAME="QY" size=82><P>

    Remember that users must type Command Queries (e.g., "features ct glass") in this box. So they will need to know field names and, if they want to do word, phrase or proximity searches, how to use CT.

    Note: You cannot use Command Query boxes (QY) and normal query boxes (QB0/QI0/QF0) on the same query screen. If you fill in the Command Query box, the contents of the normal query box will be ignored. If you leave the Command Query box blank, you'll get "Unable to recognize as a correctly formed query." if you type anything in the normal query box.


    Specifying Logo/Background Locations using DB/TextWorks

    By default, background and logo images for:

  • Query/menu screens: must reside in the /DBTW-WPD/IMAGES/ subdirectory
  • forms: reside in the location specified in the DBTWPUB.INI file
  • Note that picture boxes containing fixed images (as opposed to record images) behave the same as logo and background images.

    To specify alternate background or logo image locations, you can include the image path in the HTML Options text box (e.g., Leading Logo) where you specify the image file name in the DB/TextWorks Form Designer, Menu Screen Designer or Query Screen Designer. In order to override the default location, the image file name must include a forward slash (/). Examples:

    http://www.co.com/logos/corplogo.gif
    /backgrnd/simple.gif
    ./qbe5.gif

    Partial paths like the second two shown above are relative to the query or menu screen location (even when specified for a logo/background image in a form). The last one specifies that QBE5.GIF resides in the same directory as the query/menu screen.

    Note: This functionality does not apply to textbase image names stored in records. WebPublisher strips off all path information from image names stored in records and uses the Default-Image-Location= and [WebPublisher Image Locations] settings in DBTWPUB.INI to determine their location.


    Replacing Submit Query Button with an Image

    You can replace the button with an image.
    Note that these images are not affected by the image locations settings discussed in the previous section. You must explicitly specify their locations (e.g., as shown below).

    To replace the Submit Query button with an image, use a text editor to change the following line at the bottom the exported query screen:

    <INPUT TYPE="submit" VALUE="Submit Query">

    Change the TYPE= parameter to "image", remove the VALUE= parameter and add a SRC= parameter showing the image file name. For example:

    <INPUT TYPE="image" SRC="/dbtw-wpd/images/strtsrch.gif">


    Brief List of WebPublisher Parameters

    WebPublisher has several parameters that can be specified in a query screen, menu screen or canned query. Here is a brief listing of each of the parameters and what they are used for. Each query screen parameter overrides any equivalent setting in DBTWPUB.INI.

    ParameterPurposeEquivalent in
    DBTWPUB.INI
    ACTells WebPublisher what to do. Examples: QBE_QUERY, GET_RECORD, XML_RF_SCHEMA. 
    BGBackground color for message pages. Obtained from background color on page which generated message. 
    BUBase URL. Points to page used to generate search. 
    CSControls whether report/display pages use CSS.WebCSSOpt=
    DFSpecifies the expanded display form name. 
    DLSpecifies whether to show the form list on the expanded display page. 
    DTDocument Type. Specifies the "content" setting for the HTTP header information passed to the Web browser. 
    EFSpecifies the edit form name; also used for delete record. 
    ELSpecifies whether to show the form list on edit/delete pages. 
    ESSpecifies whether to open the expanded display in a new browser window.WebExpandInSeparate=
    FGText color for messages. Obtained from box label font color for first box on page which generated message. 
    IDSpecifies the textbase password. 
    MFSpecifies message file name for message translation.MessageFile=
    MQSpecifies name of query screen from which to read search textbase information for WebPublisher Multiple Textbase Query. 
    MRSpecifies number of records per page. 
    NPSpecifies the location of the form list and Next/Previous/New Search buttons.
    1=top, 2=bottom, 3=both
     
    QB0
    QF0
    QI0
    Specifies query criteria (boolean, field name, search criteria) for search; the number 0/1/etc., corresponds to the query screen box number, starting with 0. 
    QSSpecifies the HTML query screen file name. Used in conjunction with the textbase password cookie. 
    QYSpecifies Command query criteria for search. Alternative to QB0/QI0/QF0. 
    RFSpecifies the report form name. 
    RLSpecifies whether to show the form list on the report page. 
    RNRecord number in the current set. 
    SEEntry in the current set. 
    SNSet name. Textbase set name for menu screen queries. Temporary autoset name for other queries. 
    TITextbase Index. Used with WebPublisher Multiple Textbase Query (MQ). Specifies which textbase the record comes from. 0=lead textbase, 1=first search textbase, etc. 
    TNSpecifies textbase name. 
    TRSets the total number of records displayed by WebPublisher.TotalRecords=
    TXSets the total number of records displayed by WebPublisher when using XML output. Defaults to 1000 if not specified. Use TX=0 to return all records.TotalRecordsforXML=
    XCSpecifies whether to use CGI. Example: XC=/dbtw-wpd/exec/dbtwpcgi.exe 
    XEFor use with XML output. Specifies how errors are returned if an XSL file is specified. 0=HTML, 1=XML, 2=XML errors are transformed using the XSL.  
    XMSpecifies whether to return XML output. 
    XPSpecifies the "expires" setting for the HTTP header information passed to the Web browser. 
    XSFor use with XML output. Specifies which XSL file to use. 


    Switching between CGI and ISAPI JavaScripts

    The install program permits you to specify whether to use the CGI JavaScripts or the ISAPI JavaScripts. If you need to switch later, there are two "batch" files which permit you to do so. Run ISAPI.BAT in the \JSCRIPT subdirectory to switch to using ISAPI scripts. Run CGI.BAT in the same subdirectory to switch to using CGI scripts.


    DB/TextWorks & WebPublisher Compatibility Issues

    Are you using compatible versions of DB/TextWorks and WebPublisher?

    If you're using DB/TextWorks 7.0, you should be using WebPublisher PRO 7.0 and vice versa. (Note: The ASP file used by WebPublisher for editing records has been renamed from dbtwp-edit.asp to iwpp-edit.asp.) You do not have to upgrade WebPublisher (the read-only version) to 7.0.

    If you have added record-level security (an Access Control field) to your textbase structure using DB/TextWorks version 5.2 or later, you must use WebPublisher 5.2 or later to search that textbase.

    In WebPublisher 5.1, the syntax of the WPENGMSG.INI file for the Message Translation feature changed slightly; specifically the lines for the Next/Previous buttons. If you upgraded from an earlier version and you use the Message Translation feature, if your message INI file includes the lines for the Next & Previous buttons, either delete those lines or modify them so they match the new syntax in the new WPENGMSG.INI file.

    Forms saved using DB/TextWorks version 4 can only be seen by WebPublisher version 4 or later, not with prior versions of WebPublisher.

    If you upgraded from a version of WebPublisher before 3.0, you must use DB/TextWorks version 3 or later to re-export to HTML any query or menu screens created for the previous version of WebPublisher.


    Removing Earlier Versions of WebPublisher

    Listed below are the files installed by earlier versions of WebPublisher. You can use Windows Explorer or DOS commands to remove them once you have completed the transition to WebPublisher v4.0. Shown below are the locations where the WebPublisher installation program put the files. Certain files may have been copied or moved to other locations; for example, the Word Wheel files may have been duplicated wherever HTML query screens were stored. You also might not have all of these files, depending on what version of WebPublisher you upgraded from.

    Windows System32 Directory

    For example: C:\WINNT\SYSTEM32\

    DBTUT22R.DLL - Do not delete this file if you also have the DB/Text Update Manager or DB/Text PowerPack installed on this machine. This file is shared by all three programs. This file is also used by Inmagic DB/TextWorks version 2.2; however, its installation program puts this file in the same location as DBTEXT32.EXE.

    HTTP Program (or Scripts) Directory

    For example: C:\INETPUB\SCRIPTS\ or C:\WEBSITE\CGI-SHL\

    DBTCGI.EXE
    DBTHMLQ.DLL
    WEBPUB.HLP
    WEBPUB.CNT
    LICENSE.TXT

    HTML Data (or Document) Directory

    For example: C:\INETPUB\WWWROOT\ or C:\WEBSITE\HTDOCS\

    INMAGIC.GIF
    HELP.GIF
    DWSBEGIN.HTM
    DWS_WW.HTM
    DWSMSG.HTM

    Word Wheel Files

    BigList.class
    BitFlag.class
    BorderPanel.class
    BrowserApplet.class
    BrowserDialog.class
    FieldInfo.class
    InfoDialog.class
    MultiColumn.class
    MultiColumnCallback.class
    MultiLineLabel.class
    NSInterface.class
    ServerConnection.class
    XLEntry.class
    XList.class

    Sample Textbase Files (Optional)

    CARSQBE.HTM
    CARSQBEW.HTM
    CARSXTRA.HTM
    CARS.ACF
    CARS.BTX
    CARS.DBO
    CARS.DBR
    CARS.DBS
    CARS.IXL
    CARS.OCC
    CARS.SDO
    CARS.TBA
    CONTACTS.DMP
    MODELCO.GIF
    35FORD.JPG
    BENZ.JPG
    CORVETTE.JPG
    CRUISER.JPG
    DESERT.JPG
    FERRARI.JPG
    MAZDARX.JPG
    MUSTANG.JPG
    OUTSTOCK.JPG
    PORSCHE.JPG
    ROADBOSS.JPG
    SUPRA.JPG
    WINGER.JPG

    Query Sets Files (.wpo/.wpd)

    Previous versions stored query sets files in the directory specified by the UserFilePath= line in INMAGIC.INI. WebPublisher version 4.0 stores query sets files in the "qsets" subdirectory under the installation directory. Delete the files with extensions .WPO and .WPD in the previous location to free up disk space.


    Troubleshooting

    SymptomCommon Cause / Solution
    Multiple Javascript errors when loading a menu or query screen in a web browserThe /DBTW-WPD virtual directory has not been mapped/aliased properly to the WebPublisher installation directory or doesn't have the necessary access (Read, Execute and Scripts). Some HTTP servers (e.g., O'Reilly Website), may also require explicit access to the /DBTW-WPD/EXEC/ virtual directory.
    Netscape 4.0 occasionally displays "garbage" (javascript or scrambled reports) when pressing the Back buttonThis is a problem related to Netscape 4.0 caching. To correct the problem, press the Reload button.
    Netscape 3.0 opens a Save As dialog for dbtw-q-main.js when loading a menu or query screenThe following registry setting is required on the HTTP server machine for Netscape 3.0 to work properly with Microsoft IIS 3.0. After updating the registry, the machine must be rebooted. Normally the WebPublisher installation adds this setting to the registry.
    Location: HKEY_LOCAL_MACHINE\System\ControlSet001\Services\Inetinfo\Parameters\MimeMAP\
    String value: application/x-javascript,js,,5
    ValueData: ""
    Word Wheel buttons (except the first) appear above the matching input box with Netscape 3.0Edit the HTML query screen to add a <TD> command before the <script> command for each word wheel.
    Netscape 3.0 displays "garbage" in tabular reports including links.Netscape 3 renders Javascript within a table as visible code. Upgrade to at least version 4 of Netscape, or change the screen resolution or window size so the link fits all on one line.
    Netscape 3.0 displays "garbage" when using O'Reilly WebSite as the HTTP server.Netscape 3.0's caching does not work properly with O'Reilly WebSite 1.1f. Upgrade to a newer version of O'Reilly WebSite or at least version 4 of Netscape.


    Contacting Inmagic, Inc.

    Inmagic, Inc.
    800 West Cummings Park
    Woburn, MA 01801
    Tel: 781-938-4442
    Fax: 781-938-6393
    www.inmagic.com

    Inmagic, Inc. also provides electronic support on the Internet. You can:

    Private Email

    support@inmagic.com- product support questions
    sales@inmagic.com- sales, pricing, shipment status questions
    webmaster@inmagic.com- messages related to Inmagic's web pages
    wishlist@inmagic.com- feature requests
    inmagic@inmagic.com- other messages

    If your message is addressed to a particular person at Inmagic, Inc. (e.g., a Product Support representative who is expecting the message or files), please include that person's name in the subject and the message.

    Communication with Inmagic Users

    To connect to the online Web forums, visit the Product Support page on the Inmagic Web site.

    Download Information

    Visit Inmagic's Web site at www.inmagic.com. Also see the Product Support Knowledgebase. Software patches are available on the Product Updates page.