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 Notes||Explains how to use XML input with WebPublisher PRO.|
|DB/Text WebPublisher PRO Schema||Schema for XML input: http://support.inmagic.com/web.|
|DB/Text WebPublisher PRO Tutorial||XML tutorial using the CARS textbase|
|Inmagic DB/Text WebPublisher PRO Userís Manual||How to install and use WebPublisher PRO together with DB/TextWorks.|
|CARS textbase||A sample textbase so you can perform the tutorial in the WebPublisher PRO User's Manual.|
|Online help||Help 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 site||Start 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 clients||HTML 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 Schema||Schema 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.
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.
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.
All of the following operations use Windows NT Explorer (choose Start>Programs>Windows NT Explorer).
To set permissions for the WebPublisher installation directory tree:
To set permissions for the QSETS subdirectory (must be set after permissions for installation directory tree):
To set permissions for DBTWPUB.INI (the procedure is similar for INMAGIC.INI and DBTEXT.INI, except that only Read access is required):
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.
|DBTWPUB.INI||Textbase and image directory settings specific to WebPublisher|
|INMAGIC.INI||Options which may be shared with Inmagic DB/TextWorks|
|DBTEXT.INI||Date 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.
The Internet user account must have read and write access to this file.
[WebPublisher Textbase Paths]
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.
The Internet user account must have read rights to the directory where the textbase is located.
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.
[WebPublisher Image Locations]
[WebPublisher Logo Locations]
Note that the specified image locations must be accessible via HTTP, for example, as a virtual directory in your HTTP server properties.
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 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:
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">
You have two options:
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.
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:
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.
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">
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.
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.
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:
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.
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.
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.
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.
|[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.
|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.
|AutoIncludeValidationLinks=||On edit forms, controls whether the box labels for fields with validation lists are turned into hypertext links which display the validation list.|
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.|
1 = Selection box displayed (default)
|WebLinkINM=0||Specify the appearance of the Inmagic attribution line at the bottom of Web pages:|
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=1||Completely 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.
|ApplyBkgOpt=||Controls whether the form and box background colors are applied to 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:|
|FormBkgColor=||Specifies the page background color for reports and expanded displays if no explicit color is specified in the form:|
|[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).
|EnableSlotLog=1||Have 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.|
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.
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.
<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">
<INPUT NAME="XS" TYPE="hidden" VALUE="/directory/yourfilenamehere.xsl">
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.
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
<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>.
To disable all WebPublisher XML functionality, add the following line to the [WebPublisher Defaults] section of your DBTWPUB.INI file:
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:
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.
<?xml version="1.0" ?>
<Query xmlns="http://www.inmagic.com/webpublisher/query" detail="off">
The options are:
You have two options for specifying what fields are returned in the output:
<?xml version="1.0" ?> <Query xmlns="http://www.inmagic.com/webpublisher/query"> <QY>Findall</QY> <AC>QBE_QUERY</AC> <TN>cars</TN> <KeyFields> <KeyField>Name</KeyField> <KeyField>Features</KeyField> </KeyFields> <SortFields sort='specify'> <SortField type='sort'>Price</SortField> </SortFields> </Query>
<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.
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:
<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.
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:
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.
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">
|AC||Tells WebPublisher what to do. Examples: QBE_QUERY, GET_RECORD, XML_RF_SCHEMA.|
|BG||Background color for message pages. Obtained from background color on page which generated message.|
|BU||Base URL. Points to page used to generate search.|
|CS||Controls whether report/display pages use CSS.||WebCSSOpt=|
|DF||Specifies the expanded display form name.|
|DL||Specifies whether to show the form list on the expanded display page.|
|DT||Document Type. Specifies the "content" setting for the HTTP header information passed to the Web browser.|
|EF||Specifies the edit form name; also used for delete record.|
|EL||Specifies whether to show the form list on edit/delete pages.|
|ES||Specifies whether to open the expanded display in a new browser window.||WebExpandInSeparate=|
|FG||Text color for messages. Obtained from box label font color for first box on page which generated message.|
|ID||Specifies the textbase password.|
|MF||Specifies message file name for message translation.||MessageFile=|
|MQ||Specifies name of query screen from which to read search textbase information for WebPublisher Multiple Textbase Query.|
|MR||Specifies number of records per page.|
|NP||Specifies the location of the form list and Next/Previous/New Search buttons.|
1=top, 2=bottom, 3=both
|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.|
|QS||Specifies the HTML query screen file name. Used in conjunction with the textbase password cookie.|
|QY||Specifies Command query criteria for search. Alternative to QB0/QI0/QF0.|
|RF||Specifies the report form name.|
|RL||Specifies whether to show the form list on the report page.|
|RN||Record number in the current set.|
|SE||Entry in the current set.|
|SN||Set name. Textbase set name for menu screen queries. Temporary autoset name for other queries.|
|TI||Textbase Index. Used with WebPublisher Multiple Textbase Query (MQ). Specifies which textbase the record comes from. 0=lead textbase, 1=first search textbase, etc.|
|TN||Specifies textbase name.|
|TR||Sets the total number of records displayed by WebPublisher.||TotalRecords=|
|TX||Sets 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=|
|XC||Specifies whether to use CGI. Example: XC=/dbtw-wpd/exec/dbtwpcgi.exe|
|XE||For 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.|
|XM||Specifies whether to return XML output.|
|XP||Specifies the "expires" setting for the HTTP header information passed to the Web browser.|
|XS||For use with XML output. Specifies which XSL file to use.|
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.
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.
|Symptom||Common Cause / Solution|
|Netscape 3.0 opens a Save As dialog for dbtw-q-main.js when loading a menu or query screen||The 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.|
|Word Wheel buttons (except the first) appear above the matching input box with Netscape 3.0||Edit the HTML query screen to add a <TD> command before the <script> command for each word wheel.|
|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.|
Inmagic, Inc. also provides electronic support on the Internet. You can:
|email@example.com||- product support questions|
|firstname.lastname@example.org||- sales, pricing, shipment status questions|
|email@example.com||- messages related to Inmagic's web pages|
|firstname.lastname@example.org||- feature requests|
|email@example.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.