• You may have accessed CS/WebPublisher PRO by specifying the DLL/EXE name; this can happen if you attempt to bookmark a report page (or add it to your favorites) then use that bookmark.
• You may have attempted to use an AC value that modifies records. AC=UPDATE, etc. can only be used when you use XML to pass the commands to CS/WebPublisher PRO, not via an HTML query screen or canned query.

• move the textbase to an accessible location
• assign the necessary permissions (read access) to make the textbase visible to CS/WebPublisher PRO
• ensure that the Internet user account (e.g., IUSR_machinename) has at least read (and preferably full) rights to the ICSWEB.INI file
• ensure that the textbase location is included in the Default-Textbase-Paths= line of the [Web Defaults] section of the ICSWEB.INI file, and that the Internet user account has read write access to all of these directories
• ensure that the textbase location is explicitly specified in the [Web Textbase Paths] section of ICSWEB.INI.

Always use UNC file names when referring to directories on different machines than the HTTP server.

• The <operation> and <line number> indicated in the message.
• What you were doing at the time you received the message. Be as complete and detailed as possible.

This message could conceivably occur if the textbase or QSETS files are damaged. To check the textbase, run INMCSADMIN.EXE, and choose Check Textbase from the Manage Textbases menu.

Optionally check the Repair Structural Problems box and press OK to start the Check Textbase operation. When the process is complete, examine the report file. If there are any problems that have not been fixed, recover the textbase or restore a healthy backup copy.

If Check Textbase reports no problems, try to repeat the behavior that caused the message to appear. If you cannot do so, the server may have been low on system resources.

You can delete the textbase .WPD and .WPO files from the QSETS directory to eliminate any possibility that damage to these files is causing the message.

• In a Date field, Aug-11-95 is less than 1996, but in a Text field it is not.
• When numbers file numerically, 2 is less than 12, but when numbers file alphabetically 12 is less than 2.

• In a Date field, Aug-11-95 is less than 1996, but in a Text field it is not.
• When numbers file numerically, 2 is less than 12, but when numbers file alphabetically 12 is less than 2.

If you're searching for text that includes any of these symbols, enclose the search text in quotes or replace the symbol with a space.

If you are trying to find a term that includes a word like "P73", precede the search item with an equal sign or enclose the search item in quotes:
=P73 NL1
"P73 NL1"

• typing or pasting words and/or phrases in the query boxes
• selecting choices from droplists

• Performed a search that didn't retrieve any records.
• Clicked on a hypertext link that automatically performs a search.

• If the search screen includes Word Wheel or Browse Choices buttons, you can use them to open a dialog box from which you can paste words and/or terms into the search screen.
• If the search screen includes an "Enter password:" box, be sure you used a password that provides access to the fields you are searching.
• Examine the contents of the search screen (especially if it is longer than the screen) to verify that you don't have query criteria left over from a previous search.
• You must use symbols (&/!) not words (and,or,not) for Boolean operators.
• If your search includes any Boolean operators (/ & !) or range searches (:), put spaces around the symbol.
• Remember that range searches involving partial dates start from the beginning of the range. For example: <1993 will not retrieve 1-Jan-93, but >1993 will.

If you are trying to find a term or phrase that includes a word like "W2", precede the search item with an equal sign or enclose the search item in quotes:

You may be searching for text that actually has a colon in it, rather than attempting to perform a range search. If this is the case, either omit the colon or enclose the text in quotes (e.g., "TX : Texas"). Depending on how the webmaster has configured CS/WebPublisher PRO , another solution would be to remove the spaces around the colon (TX:Texas). Punctuation is not significant except in Code or UDC fields, so it's usually easier to omit punctuation in search text.

The record has been deleted using deferred indexing. When the deferred updates are posted, the record will be removed from the textbase, so making any changes to it is pointless.

You used Substitute Text or Substitute Matching Entry, and the text or complete entry was not found in the record. This is normal, especially if you didn't explicitly search for records containing that text or entry. For example, you could do a Find All Records and change all "[" to "(".

If you received this message when clicking on a hypertext link, textbase fields or sets may have been renamed since the menu screen was created.

• Mismatched quotes or parentheses
• Extra Boolean operators (e.g., you should have typed "car / auto" instead of "car / auto /")

If you cannot determine what caused the error, try a couple of simpler searches, e.g., just a word in a box, to see if they work. If the search screen includes Word Wheel or Browse Choices buttons, use those to reconstruct the query.

If even simple searches don't work, contact the webmaster for the site, tell them you received this message, and describe what you typed in each box. The search screen may need to be edited and corrected. If there are multiple copies of the textbase with the same name, the webmaster may need to verify that the [Web Textbase Paths] section of the ICSWEB.INI file references the correct path. (For DB/Text WebPublisher PRO , check the [WebPublisher Textbase Paths] section of DBTWPUB.INI.)

• The record was submitted for UPDATE with matchFound="appendEntries".
• The field name specified at the end of the message has 'Single Entry Only' validation.
• The incoming record contains a single entry in that field. (If the import file contained more than one entry in that field, you would receive a different message.)
• The matching record in the textbase already contains an entry in that field.

• Automatic Date
• Automatic Number
• Computed Date
• Computed Number

These field types are updated automatically, and cannot be edited.

If the search screen does not have an "Enter password:" box, contact the webmaster for the site. One will need to be added so that people can search the textbase.