BUG: Hit-Highlighting Problem Using CONTAINS Prefix Expansion

ID: Q186376

The information in this article applies to:

• Microsoft OLE DB Provider for Index Server, version 2.0

SYMPTOMS

When you run the SQL sample that comes with Index Server 2.0 and query for a string with prefix expansion (such as 'CONTAINS(' "Inter*" ')>0'), the query results display correctly and you see "Summary" and "Full" links. However, no words are hit-highlighted.

CAUSE

This is a problem in the way the Microsoft OLE DB Provider for Index Server 2.0 generates "Query Restriction" to handle use of hit-highlighting. This is caused by RS.Properties("Query Restriction") that returns

'(@contents("Inter*"))'.

RESOLUTION

Currently there is no resolution to the problem.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Microsoft OLE DB Provider for Index Server 2.0 supports searching for Prefix Expansion (wildcards) in the CONTAINS predicate of the WHERE clause of a SQL statement.

Following is the correct syntax to use Prefix Expansion (wildcards) in the CONTAINS predicate of the WHERE clause of a SQL statement:

   CONTAINS ( [ column_reference, ] ' "Word_or_Phrase*"
   [ Boolean_Operator "Word_or_Phrase" ] ... ' ) > 0

REFERENCES

For more information on Index Server, please refer to Index Server documentation in the Windows NT Option Pack documentation.

Additional query words: kbDSupport kbIndexServer kbDatabase kbOLEDB kbdse

Technology        : ole
Version           : WINDOWS:2.0
Platform          : WINDOWS
Issue type        : kbbug
Solution Type     : kbpending

Last Reviewed: June 2, 1998