Link is showing a “No Match!” error?
A “No Match!” condition means the AutoPrice Link (placeholder) has been assigned to a Search Key that does not exist in the database file. The purpose of this error is to indicate when a product number record has been removed from the database file.
Please note that "No Match!" is the default setting for this error in the document. By editing the AutoPrice preferences or settings for individual Variable Links, it can be changed to a custom error string.
Confirm the "No Match!" Link's Assigned Search Key is not in the database file.
- Insert the text cursor into the “No Match!” Link (the placeholder that encountered the “No Match” condition when it was updated) by clicking on it with the appropriate tool.
- Open the AutoPrice floating palette. Check if the palette is in Table-Tagger mode, put the palette in Search Key mode by clicking on the TT icon in the upper left corner of the palette.
- The Search Key setting on the palette will show you the search key that is assigned to that “No Match” placeholder. Note the search key that is displayed on the palette (or copy the search key to your clipboard so you can paste it into a find window next).
- Open the database text file and look for that search key value, to confirm that it does in fact exist in the current listing of records that AutoPrice is working with.
- If there is a record that does contain that search key, confirm there are no invisible characters (for example, extra spaces) in that field. If there are any invisible characters, you now know why the AutoPrice cannot find the Search Key Value assigned to the link that is showing the error.
- If you cannot find an exact match in the database file, then you know that the placeholder has encountered a error condition because the placeholder is assigned to a search key value that does not exist in the database file. This is the intended meaning of this error.
- If you can find an exact match in the database file and if your database file is using a double quote as a Text Qualifier, then confirm any inch mark characters are represented by two consecutive double quote characters instead of just one single double quote character. This also applies to any double quote character that is part of the text string that is inside the field. Do not double the double quote characters that are being used for Text Qualifiers.
- Next, confirm that the Database Definition that you are using has the correct settings, as described in the next set of steps.
Confirm the DDF has correct settings.
- Open the Database Definitions window by opening the AutoPrice menu and selecting Setup > Database Definitions.
- For the “Current DDF” selection on the Database Definitions window, choose the DDF that you were using when you encountered the “No Match!” condition, and then click the “Edit” button.
- This will open the Edit DDF window where you can confirm the Search Key Field, the Case-Sensitive Search, Field Delimiter, File Origin, and Text Qualifier settings are the correct settings for the database file that you are using to update the documents.
- Change these settings if they are not set appropriately for the current database file, then click OK to close the Edit DDF window. This will return you to the Database Definitions window where you are now ready to click the OK (or Select on older versions) button which will close the Database Definitions window and will assign the Current DDF to the document.
- If you changed any DDF settings, to confirm AutoPrice is now able to update the placeholder, update the “No Match!” placeholder (click inside the “No Match!” placeholder and then click the Update button on the AutoPrice palette).
- If the placeholder is still encountering a “No Match!”, or if you did not change the original settings for the DDF because they appear to be correct, then contact Meadows Support for assistance. For information, see Contacting Meadows Support).