Inmagic DB/Text WebPublisher v6.1 Messages

Inmagic® DB/Text® WebPublisher version 6.1
Error Messages

DB/Text WebPublisher PRO 1.0 corresponds to DB/Text WebPublisher 6.1.
If you cannot find a message which contains the word "Lite," look for the same message with "Lite" omitted.

Cannot create temporary storage file for query sets. Contact the webmaster for this site.

Cause	The directory where temporary DB/Text WebPublisher sets are stored is write protected or does not exist.
Solution	The webmaster for the site where the textbase resides needs to verify that the "qsets" subdirectory under the WebPublisher installation directory exists and is visible to the HTTP server, and that the Internet user account has full (read, write, create) access to this directory.

Cannot find field '<field name>'.

Cause	The field indicated in the message does not exist. The field may have been renamed or deleted since the query screen was created.
Solution	Contact the webmaster for the site where the textbase resides, and provide the exact text of the message. The webmaster will probably need to modify the query screen or edit the textbase structure to correct the problem.

Cannot find or load set '<set name>'.

Cause	You clicked a link which includes the named set as part of its query criteria. The query set indicated in the message does not exist. The set may have been renamed or deleted since the page was created.
Solution	Contact the webmaster for the site, and provide the exact text of the message, the URL for the page and the text of the link you clicked. The webmaster will probably need to modify the page or recreate the set to correct the problem.

Cannot recognize entry in field '<field name>' as a date.

Product	DB/Text WebPublisher PRO
Cause	The field indicated in the message has a Field Type of Date and has 'Require Strictly Correct Type' checked in the textbase structure. WebPublisher PRO cannot recognize the entry you tried to create as a date.
Solution	Enter a valid date in the field.

Cannot recognize entry in field '<field name>' as a number.

Product	DB/Text WebPublisher PRO
Cause	The field indicated in the message has a Field Type of Number and has 'Require Strictly Correct Type' checked in the textbase structure. WebPublisher PRO cannot recognize the entry you tried to create as a number.
Solution	Enter a valid number in the field.

Cannot save an empty record.

Product	DB/Text WebPublisher PRO
Cause	The record you attempted to insert does not contain any fields. Either no field tags are specified in the XML input, or the field contents are empty/null or just spaces.
Solution	Type something in at least one of the fields before you try to save the record.

Cannot search unindexed field '<field name>'.

Cause	The field indicated in the message has neither a Term index, nor a Word index. DB/Text WebPublisher cannot search unindexed fields. The indexes were removed after the query screen was designed.
Solution	The webmaster for the site where the textbase resides needs to use Edit Textbase Structure to add either a Term index or a Word index or both to this field.

Could not access XML conversion facility.

Cause	You shouldn't normally see this message. It indicates that WebPublisher could not access the XML conversion facility.
Solution	The webmaster for the site where the textbase resides will need to ensure that the Microsoft XML program files are properly installed and accessible to WebPublisher.

Could not check for matching records because indexes are busy.

Product	DB/Text WebPublisher PRO
Cause	The indexes are tied up because they are being updated to match the changes to a record. You cannot search if the indexes are being changed. Checking for matching records uses searching.
Solution	Wait a little while, then try again.

DB/Text WebPublisher cannot be accessed in this way.

Cause

In the call to WebPublisher, the AC= parameter has either been omitted or is specifying an invalid value. For example:

You may have accessed DB/Text WebPublisher 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 which modifies records. AC=UPDATE, etc. can only be used when you use XML to pass the commands to WebPublisher, not via an HTML query screen or canned query.

Solution

You cannot bookmark the results of a WebPublisher query. Aside from this issue, temporary query sets expire periodically. Instead, bookmark the query or menu screen and repeat the search.

Use XML to pass UPDATE, INSERT, DELETE and BATCH_DELETE commands to WebPublisher.

DB/Text WebPublisher cannot modify records because it does not have write access to the textbase.

Product	DB/Text WebPublisher PRO
Cause	The account used by WebPublisher PRO (often IUSR_machinename) does not have Full rights to the directory containing the textbase. Or the textbase is write-protected using file permissions.
Solution	Contact the webmaster for the site. They will need to use Windows Explorer to provide the necessary rights to the directory containing the textbase, or remove the Read-Only attribute on the textbase files. If WebPublisher is using the IUSR_machinename account, that account will need to be explicitly added to the Security properties; IUSR_machinename is not a member of the various groups (EVERYONE, USERS, etc.).

DB/Text WebPublisher cannot modify records because you did not specify any records to modify.

Product	DB/Text WebPublisher PRO
Cause	The XML input for an INSERT, UPDATE or DELETE doesn't have a <Recordset> section.
Solution	Contact the webmaster for the site. The page which creates the XML input will need to be modified to add the <Recordset> tag.

DB/Text WebPublisher could not find textbase '<textbase>' on the server.

Cause

This message may appear after you press the Search button on the "Inmagic DB/Text WebPublisher: Find Textbase" page. The textbase specified in the message is not visible to the HTTP server.

Solution

Contact the site administrator. They will need to do one or more of the following:

- move the textbase to an accessible location
- assign the necessary permissions (read access) to make the textbase visible to the HTTP server
- ensure that the Internet user account (e.g., IUSR_SERVERNAME) has at least read (and preferably full) rights to the DBTWPUB.INI file
- ensure that the textbase location is included in the Default-Textbase-Paths= line of the [WebPublisher Defaults] section of DBTWPUB.INI, 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 [WebPublisher Textbase Paths] section of DBTWPUB.INI.

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

The DB/Text WebPublisher DLL has not been properly serialized.

Cause	The serial number is not a valid DB/Text WebPublisher serial number. The most likely cause for this is that the DBTWPUB.DLL file has been damaged or the installation process failed prior to completion.
Solution	The webmaster for the site where the textbase resides needs to reinstall DB/Text WebPublisher from the original disks using the SETUP program.

DB/Text WebPublisher found textbase ‘<textbase>’ - you may re-execute your query (press Back twice).

Cause	This message appears after you press the Search button on the "Inmagic DB/Text WebPublisher: Find Textbase" page. WebPublisher found the textbase.
Solution	Press your web browser's Back button twice to return to the query or menu screen. Then re-execute your query. If doing so returns you to the "Inmagic DB/Text WebPublisher: Find Textbase" page, the Internet user account does not have the required full access to the DBTWPUB.INI file. Contact the webmaster for the site.

DB/Text WebPublisher internal error <code>. Please contact Inmagic, Inc.

Cause	A condition occurred which the software did not expect.
Solution	Send the following information to Inmagic, Inc. or your local Inmagic dealer: The <code> 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. In DB/TextWorks, choose Check Textbase from the Manage Textbases menu (and optionally check the Repair Problems box). When the process is complete, examine the report file. If there are any problems which have not been fixed, recover the textbase or restore a healthy backup copy. If Check Textbase reports no problems, try to repeat the behavior which 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. Regardless of whether the textbase is damaged, or you can repeat the problem, please do forward the information to Inmagic, Inc.
Notes	To also write internal errors to a log file named WPTCERR.LOG file in the QSETS directory, add EnableErrorLog=1 to the [WebPublisher] section of your DBTWPUB.INI file.

DB/Text WebPublisher Lite cannot access textbase '<textbase name>'.

Cause	The textbase name specified in the query or menu screen (and shown in the message) does not match the textbase name specified in the [WebPubLite] section of the DBTWPUB.INI file.
Solution	The webmaster for the site needs to see the READMEWP.HTM file for instructions. To search multiple textbases, upgrade to DB/Text WebPublisher.

The DB/Text WebPublisher Lite textbase path or name is not initialized.

Cause	The textbase name or path is not specified in the [WebPubLite] section of the DBTWPUB.INI file.
Solution	The webmaster for the site needs to see the READMEWP.HTM file for instructions.

The DB/Text WebPublisher Multiple Textbase Query screen has been renamed or deleted. Please contact the webmaster for this site.

Cause	This HTML query screen searches multiple textbases. The textbase query screen which indicates which other textbases to search is no longer available.
Solution	The webmaster for the site where the textbase resides needs to recreate the saved public query screen specified by the MQ= parameter in the HTML query screen.

DB/Text WebPublisher Trial Version cannot open a textbase containing more than 50 records.

Cause	The site where the textbase resides is using a trial version of DB/Text WebPublisher.
Solution	The webmaster for the site where the textbase resides needs to (purchase and) install a full version of DB/Text WebPublisher. If the textbase is strictly for demonstration/testing purposes, they can delete enough records so the textbase has fewer than 50 records.

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

Cause	The webmaster for the site where the textbase resides has disabled XML output for either WebPublisher or this textbase.
Solution	Contact the webmaster for the site about enabling XML for this textbase.

Entry in field '<field name>' does not match the expected format '<mask>'.

Product	DB/Text WebPublisher PRO
Cause	The field indicated in the message has mask validation. The text you typed does not comply with the mask shown in the message.
Solution	Change what you typed to comply with the mask shown in the message. Mask characters: # - digit (0-9) ! - capital letter ^ - lowercase letter ? - any character including space * - any group of characters including space

Entry in field '<field name>' is above the maximum value '<maximum>'.

Product	DB/Text WebPublisher PRO
Cause	The field indicated in the message has range validation. The text you typed is greater than the maximum value shown in the message.
Solution	Change what you typed to be less than the maximum value shown in the message.
Notes	Field Type and Special Filing options affect whether a value is greater than the maximum value permitted by the range validation. Examples: 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.

Entry in field '<field name>' is below the minimum value '<minimum>'.

Product	DB/Text WebPublisher PRO
Cause	The field indicated in the message has range validation. The text you typed is less than the minimum value shown in the message.
Solution	Change what you typed to be greater than the minimum value shown in the message.
Notes	Field Type and Special Filing options affect whether a value is less than the minimum value permitted by the range validation. Examples: 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.

Entry in field '<field name>' not found in validation list: <entry>

Product	DB/Text WebPublisher PRO
Cause	The field indicated in the message has a validation list. The entry shown in the message does not appear in the validation list.
Solution	The field entry must exactly match an entry that appears in the validation list, including spacing and punctuation. If case differs, it is corrected automatically when you save the record. The webmaster for the site can also use the validation=update/override attribute on the <AC> tag to permit entries which are not in the validation list.

Entry in field '<field name>' should be unique, but is not.

Product	DB/Text WebPublisher PRO
Cause	The field indicated in the message has a Unique Entries Only validation. The entry you typed already appears in another record in the textbase.
Solution	Type a unique entry in the field. You can see a list of entries in the field by using the Word Wheel on an HTML query screen.

Error loading XML stream - <reason>. <line number>

Cause	The query screen you used to do the search generates XML output which is then transformed by an XML style sheet (XSL) file. WebPublisher encountered an error when attempting to load the XML generated by WebPublisher before transforming it. The message normally includes the reason for the error and the line number in the XML stream on which the problem occurs.
Solution	The webmaster for the site must correct the problem. If using a Web browser which can transform XML output (e.g., IE5.x or later), one can temporarily stop using the XSL file, and display raw XML in the Web browser, to get more information about the line which is causing the error.

Error reading XML file '<XML file>' - <reason> line <line number>

Cause	The screen you used generates XML output. WebPublisher encountered an error reading the specified XML file. The message includes the reason for the error and the line number in the XML file on which the problem occurs.
Solution	Contact the webmaster for the site and tell them exactly what you did to generate the error.

Error reading XSL file '<XSL value>' - <reason> line <line number>
Error reading XSL file '<XSL value>' (from '<URL>').

Cause

The query screen you used to do the search generates XML output which is then transformed by an XML style sheet (XSL) file. The <XSL value> shown in the message indicates the value of the XSL= parameter specified in the query screen.

WebPublisher encountered an error reading the specified XSL file. The message includes the reason for the error and the line number in the XSL file on which the problem occurs. If no reason or line number is given, WebPublisher cannot find the XSL file (the '<URL>' shows the complete URL to which any relative URL was translated), or the XSL file is too unreadable to report a specific problem.

Solution

The webmaster for the site must either fix the problem in the XSL file, or specify the correct location of the XSL file.

Error transforming XML file '<XML file>'.

Cause	The screen you used generates XML output, which is then transformed by an XML style sheet (XSL) file. There is a mismatch between the XML file and the XSL stylesheet file.
Solution	Contact the webmaster for the site. They will need to modify the XSL file.

Error trying to initialize the XML conversion facility.

Cause	There is a problem with the Microsoft XML4 program file installation. The MSXML4 DLLs either are not properly installed, are damaged, or are not accessible to WebPublisher. The WebPublisher install puts these files in the Windows System directory.
Solution	The webmaster for the site must ensure that the Microsoft XML4 DLLs are properly installed, and that the account used by WebPublisher has sufficient rights to use these files.

Field '<field name>' is not a Link field.

Cause	The DB/Text WebPublisher search screen you are using is not compatible with the textbase it searches. The textbase structure has been changed since the search screen was created. A box searches a secondary textbase field (e.g., Title@Catalog). The message indicates that 'Catalog' is a field in the current primary textbase but it is not a Link field.
Solution	The webmaster for the site where the textbase resides needs to create a new search screen for this textbase. For now, you can only search the textbase if you don't use that box.

Field '<field name>' uses a thesaurus as a validation list, and the thesaurus textbase cannot be found.

Product	DB/Text WebPublisher PRO
Cause	The field specified in the message has "Use Thesaurus as Validation List" specified in Edit Textbase Structure, but the thesaurus textbase cannot be found or opened.
Solution	Contact the webmaster for this site. They will need to verify that the thesaurus textbase is in the location shown by Maintain>Set Up Thesaurus in DB/TextWorks.

Field must have a value: <field name>

Product	DB/Text WebPublisher PRO
Cause	The field indicated in the message has 'Field Entry Required' validation selected in the textbase structure. An INSERT or UPDATE statement left this field empty. The record cannot be saved until this field is populated.
Solution	Type a valid entry in the field and save the record again.

Field occurs more than once: <field name>.

Product	DB/Text WebPublisher PRO
Cause	There is a problem with the XML input. The field name shown in the message occurs more than once in the incoming record, separated by other fields.
Solution	In the <Record> in the XML input, repeating entries for the same field must be grouped together. The following is NOT correct because the entries in the Features field are not together: <Record> <Product-Number>LW0001</Product-Number> <Features>Glass</Features> <Name>Miata</Name> <Features>Glass</Features> </Record>

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 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.

You can also contact the webmaster for the site where this textbase resides and ask them to use Edit Textbase Structure to add a Term index to the field.

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 query 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"

You can contact the webmaster for the site where the textbase resides and ask them to use Edit Textbase Structure to add a word index for that field.

Found multiple records in textbase that match the record in the incoming data.

Product	DB/Text WebPublisher PRO
Cause	You attempted to update an existing record. For the record which follows the message, there is more than one record in the textbase which has matching information in the specified Match Fields.
Solution	For the matching fields, specify a field (or combination of fields) which is unique in each record (e.g., an Automatic Number field or a field with Unique Entries Only validation).

Found no matching record in textbase to delete.

Product	DB/Text WebPublisher PRO
Cause	You attempted to delete a record. For the record which follows the message, there is no record in the textbase which has matching information in the specified Match Fields.
Solution	Check that the contents of the Match Fields match a record in the textbase.

Incorrect password entered.

Cause	The DB/Text WebPublisher search screen contains an "Enter password:" box. You typed a password which is not in use for this textbase.
Solution	Return to the search screen and type a valid password. The textbase may have a Silent password. If you don't know a password, try leaving the "Enter password:" box blank.

Link entry in field '<field name>' not found in secondary textbase.

Product	DB/Text WebPublisher PRO
Cause	The field indicated in the message is a Link field with 'Require Strictly Correct Type' checked. The entry you typed does not appear in the matching associated field in the secondary textbase.
Solution	Change the field contents so they match the contents of the associated field in a record in the secondary textbase. If you have a query screen which has a Word Wheel for that secondary textbase field, you can browse the index.

Link '<field name>' not valid or not available.

Cause

You typed a search which attempted to search a field from a secondary textbase. You cannot search secondary textbase fields until the problem is corrected.

Solution

If the textbase has passwords, the password you are using may hide the linked information. Return to the search screen and specify a password gives you access to the linked information.

Otherwise, contact the webmaster for the site where the textbase resides, and provide the exact text of the message. The webmaster will probably need to use Edit Textbase Structure to correct the problem. For example, the secondary textbase may not have a Silent password.

MatchField has no Term index: '<field name>'.

Product	DB/Text WebPublisher PRO
Cause	A MatchField specified in the XML input does not have a Term index. WebPublisher PRO uses the Term index to determine whether the incoming record matches a record already in the textbase.
Solution	Contact the webmaster for the site. They need to either use Edit Textbase Structure in DB/TextWorks to give the MatchField a Term index, or modify the page which submits the XML input so that it uses a different field name.

Multiple entries are not permitted in field '<field name>'.

Product	DB/Text WebPublisher PRO
Cause	The field indicated in the message has a has 'Single Entry Only' validation. You tried to save the record when the field contained multiple entries.
Solution	You must remove all but one before you will be able to save the record.

No query criteria specified.

Cause	You pressed the Submit Query button without specifying any query criteria, either by: - typing words and/or phrases in the query boxes - selecting choices from droplists
Solution	Specify what you want to search for before pressing the Submit Query button.

No records found by latest query.

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 Word Wheel buttons, use the word wheel to paste words and/or terms into the search screen.

- If the search screen includes an "Enter password:" box, be sure you used a password which 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 got this message when you clicked on a hypertext link, contact the webmaster for the site where the textbase resides. The query criteria for the stored set may need to be corrected.

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 query criteria 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 criteria are complex or your query 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 webmaster has configured DB/Text WebPublisher, 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". You might also want to contact the webmaster for this site about changing the query screen or indexing settings.

Record is locked.

Product	DB/Text WebPublisher PRO
Cause	The record you are trying to update or delete is locked by another user. The other person could may be editing the record, or using Batch Modify or Import (or even Batch Delete).
Solution	Wait till the other person finishes changing the record. Before attempting to modify the record again, verify that their changes do not invalidate any changes you were planning to make.

Severe error during transform using XSL file '<XSL value>'.

Cause	The query screen you used to do the search generates XML output which is then transformed by an XML style sheet (XSL) file. The Microsoft XML DLLs which are used to perform the transform performed an illegal operation. The XSL file may be damaged. The problem is so severe that no line number can be given. <XSL value> represents the value of the XSL parameter.
Solution	The webmaster for the site must address the problem with the XSL file.

Severe error loading XML stream.

Cause	WebPublisher encountered an error creating the XML output stream. This message should rarely occur. If it does, the server running WebPublisher may be running low on memory.
Solution	The webmaster for the site must address the problem with the server machine.

Severe error loading XSL file '<XSL value>'.

Cause	The query screen you used to do the search generates XML output which is then transformed by an XML style sheet (XSL) file. The Microsoft XML DLLs which are used to perform the transform performed an illegal operation. The XSL file may be damaged. The problem is so severe that no line number can be given. <XSL value> represents the value of the XSL parameter.
Solution	The webmaster for the site must address the problem with the XSL file.

The textbase ‘<textbase>’ has not yet been located on the server.

Cause	The location for the textbase name shown in the message is not yet specified in the [WebPublisher Textbase Paths] section of DBTWPUB.INI. Nor is the textbase located in any of the top-level directories specified in the Default-Textbase-Paths= line of the [WebPublisher Defaults] section.
Solution	Press the Search button to locate the textbase and write its location to the [WebPublisher Textbase Paths] section of DBTWPUB.INI. WebPublisher will do a recursive subdirectory search of the locations specified in the Default-Textbase-Paths= line.

The textbase‘<textbase>’ must have a Silent password. Contact the webmaster for this site.

Cause	The query screen you used to Submit the query searches multiple textbases. Some of the textbases have passwords but no Silent password.
Solution	The webmaster for the site where the textbase resides needs to assign a Silent password to the textbase name shown in the message.

There is a Boolean expression which is too deeply parenthesized.

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"

This DB/Text WebPublisher DLL has expired.

Cause	The site is using a trial version of DB/Text WebPublisher, and the trial period is over.
Solution	Contact the webmaster for the site and tell them you received this message.

This link does not have a valid destination (set no longer exists in textbase). Please contact the webmaster for this site.

Cause	You clicked on a hypertext link which performs a search "under the covers". The query set referenced by the hypertext link has been deleted from the textbase or renamed. This message may also appear if one of the fields referenced by the set has been renamed.
Solution	Contact the webmaster for the site about correcting the HTML page or restoring or recreating the query set.

Trailing text is not permitted in field '<field name>'.

Product	DB/Text WebPublisher PRO
Cause	The field indicated in the message has a Field Type of Date or Number and has 'Require Strictly Correct Type' checked in the textbase structure. 'Allow Trailing Text' is not checked. The text in the field does start with a valid date or number, but includes additional text after the date/number.
Solution	Remove the trailing text before you attempt to save the record again.

Transform using XSL file '<XSL value>' produced no result.

Cause	The query screen you used to do the search generates XML output which is then transformed by an XML style sheet (XSL) file. The result of the tranform is an empty page.
Solution	The webmaster for the site must fix the problem with the XSL file.

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	Contact the webmaster for the site and tell them you received this message. The webmaster may need to increase the maximum textbase users, or add passwords to prohibit exclusive access.

Unable to recognize as a correctly formed query.

Cause

DB/Text WebPublisher cannot understand the search criteria typed in the search screen. This is a general error message which is often caused by typographical errors, or problems with the search screen.

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.

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 Word Wheel 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 [WebPublisher Textbase Path] section of the DBTWPUB.INI file references the correct path.

If you received the message when clicking on a hypertext link, contact the webmaster for the site and tell them what link you clicked on. The hypertext link may need to be edited and corrected.

Unknown field name: '<field name>'

Product	DB/Text WebPublisher PRO
Cause	A field name specified inside a <Record> for an INSERT, UPDATE or DELETE doesn't exist in the textbase structure, or is hidden by the password you are using.
Solution	Try using a different password. If that doesn't work, contact the webmaster for the site. They may need to modify the page which submits the XML input so that it uses the correct field names.

Unknown KeyField name: '<field name>'

Product	DB/Text WebPublisher PRO
Cause	A KeyField specified in the XML input either does not appear in the textbase structure or is hidden by the password you are using.
Solution	Use a different password. If that doesn't work, contact the webmaster for the site. They may need to modify the page which submits the XML input so that it uses the correct field name.

Unknown MatchField name: '<field name>'

Product	DB/Text WebPublisher PRO
Cause	A MatchField specified in the XML input either does not appear in the textbase structure or is hidden by the password you are using.
Solution	Use a different password. If that doesn't work, contact the webmaster for the site. They may need to modify the page which submits the XML input so that it uses the correct field name.

You cannot add or change a protected field.

Product	DB/Text WebPublisher PRO
Cause	The record you are trying to insert or update includes fields which the password you are using makes read-only.
Solution	Specify a password which gives you full access to all the fields in the incoming records.

You cannot delete records because your password does not have full access to all fields in the textbase. At least one field is protected (hidden or read-only).

Product	DB/Text WebPublisher PRO
Cause	You cannot delete records without full access to all fields. The textbase has passwords. The password you are using, which may be the Silent password, hides or write-protects at least one field.
Solution	Use a different password.

You do not have write access to the record.

Product	DB/Text WebPublisher PRO
Cause	The textbase has record level security passwords. The password you are using does not permit you to modify the record you are trying to UPDATE or DELETE.
Solution	Use a different password.

You must enter a password to access the textbase.

Cause

The textbase has passwords. You must type a password to search the textbase.

Solution

Return to the search screen and type a valid password in the "Enter password:" box.

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.

If you got this message after clicking on a hypertext link, the link performs a search on the textbase. Contact the webmaster for the site. They will need to add a Silent password to the textbase.

You must specify one or more MatchFields when updating or deleting records.

Product	DB/Text WebPublisher PRO
Cause	The XML input for an UPDATE or DELETE omits the <MatchFields> section. You must indicate which fields you want to use for matching.
Solution	Contact the webmaster for the site. They will need to modify the page to include the <MatchFields> section.

Your current query has expired. Perform the search again.

Cause	This error indicates that the slot occupied by a query set has been reused by someone else's query. This may indicate that too much time has passed since the query was first performed, or that many users are searching the textbase simultaneously.
Solution	Contact the webmaster for the site. They may need to increase the maximum number of query sets that can be stored by increasing the WebSetMax= value specified in the [WebPublisher] section of the DBTWPUB.INI file in the Windows directory on the HTTP server.

Your password does not allow you to create records.

Product	DB/Text WebPublisher PRO
Cause	The password you are using does not give you full access to all fields with Field Entry Required validation. You must have full access to all required fields to create new records -- otherwise there would be no way to fill them in. The records you tried to insert did not contain those required fields. (Otherwise you would have received different messages.)
Solution	Use a password with full access to all required fields.