Inmagic® DB/Text® WebPublisher version 7.0
Error Messages (partial list)

Field(s) not indexed for comparison searching (no term index).

Cause Your search includes an operation which requires a Term index (e.g., a range search {indicated by a colon}, or a =, >, >=, <, or <= search). The field searched by the box where you typed the comparison search doesn't have a Term index.
Solution Change your search so it doesn't use any of the comparison operators. For example, if you searched for =Accounting, search for Accounting instead.

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

Field(s) not indexed for proximity searching (no word index).

Cause The search criteria include a proximity search (e.g., "bugs p2 bunny") on a field which doesn't have a word index. Proximity searches require a word index.
Solution Examine the contents of your search screen for a string like "w3" or "p5". Then change your search so it doesn't do a proximity search in that search box.

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

No search term(s) specified.

Cause You pressed the Search button without specifying any search term(s), either by:

- typing words and/or phrases in the search boxes
- selecting choices from droplists

Solution Specify what you want to search for before pressing the Search button.

No results were found.

Cause You did one of the following:
1. Performed a search which didn't retrieve any records.
2. Clicked on a hypertext link which automatically performs a search.
Solution Return to the DB/Text WebPublisher search screen and click the Help icon to review the instructions for searching. If you believe the search should have retrieved records, here are some things to check:

- If the search screen includes Browse Index buttons, use the Browse Index to paste words and/or terms into the search screen.

- Examine the contents of the search screen (especially if it is longer than the screen) to verify that you don't have search term(s) 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.

Proximity search available only for words, not phrases.

Cause Proximity only works between two words, not between multiple words or phrases. The box contents which contain the problem search string are shown in the message.

Permitted proximity searches: jelly p2 beans, govern* w5 contract*
Invalid searches: licorice p2 jelly beans, licorice p2 jelly w5 beans

Solution Examine the contents of your search screen for the string shown in the message. Then change your search so proximity operators are used only between two single words.

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

=Employee copy W2 form <-- term search
"Employee copy W2 form" <-- phrase search

Range operation is incorrect because '<beginning of range>' is not less than '<end of range>'.

Cause Your search term(s) include a range search but the beginning of the range you specified is larger than the end of the range.
Solution Look for the range search. It will have a colon in it. If the search term(s) are complex or your search screen is taller than the screen, you can use the Find option in your web browser to search for ':'. Then change the range search so the start of the range is to the left of the colon. For example, search for 20:50.

You may be searching for text which 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 textbase is configured, 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 box may search multiple fields which have different indexing settings. For example, one may treat numbers numerically, while the other may treat them alphabetically. In such a case, either "2:12" or "12:2" will cause this error. You must change your search; paste individual entries or use ">=2 & <=12" instead of "2:12".

The search is too complex.

Cause The search is too complex; there are too many levels of parentheses.
Solution If there are unnecessary parentheses, remove them.
Rearrange the order of the search items so fewer parentheses are necessary. Perform / searches before & and ! searches. For example, change "bugs & (rabbit / bunny)" to "rabbit / bunny & bugs"

Unable to access the textbase.

Cause There are several reasons why you might get this error.

- The textbase may be damaged.

- There may be too many people using the textbase.

- Someone else may have exclusive access to the textbase. For example: backup software, or someone using Check Textbase, Immediate Indexing, or editing the textbase structure.

Solution Try your search again. If the problem persists, contact the Policy Coordinator and tell them you received this message.

Unrecognizable search.

Cause DB/Text WebPublisher cannot understand the search term(s) typed in the search screen. This is a general error message which is often caused by typographical errors, or problems with the search screen.
Solution Return to the search screen and click on the Help link to review the instructions for searching. Possible problems include:

- 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 Browse Index buttons, use those to reconstruct the search.

If even simple searches don't work, contact the Policy Coordinator, tell them you received this message, and describe what you typed in each box.

Your current search has expired. Perform the search again.

Cause This error indicates that the slot occupied by a search set has been reused by someone else's search. This may indicate that too much time has passed since the search was first performed, or that many users are searching the textbase simultaneously.
Solution Try your search again. If the problem persists, contact the Policy Coordinator.