Assume that you have some databases in Microsoft SQL Server Compact 3.5. When you run a query that uses a LIKE operator in a WHERE clause, incorrect results are returned. This issue occurs when the following conditions are true:
- The LIKE pattern contains a Japanese Kana accent character.
- The LIKE pattern contains a wildcard character, such as "%abc%".
- A character before the Japanese Kana accent character partly matches the LIKE pattern.
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must exit all applications that are using SQL Server Compact 3.5. Then, you must uninstall SQL Server Compact 3.5.
Note This SQL Server Compact hotfix contains a complete .msi package and does not replace a partial list of files from a previous installation of SQL Server Compact.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.