FIX: ListBox Extended Matching Does Not Work for Hebrew or Czech Characters

This article was previously published under Q327574
This article has been archived. It is offered "as is" and will no longer be updated.
The extended matching feature of the intrinsic ListBox control causes the list box selection to change automatically to the first matching entry as you type a letter on the keyboard.

However, the extended matching feature does not work when you type entries in Hebrew or Czech.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

Note You must have a Visual Studio license agreement to obtain this hotfix.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date          Time       Version      Size        File name      Platform   -------------------------------------------------------------------------   10-Aug-2002   02:16:03    1,884,160   Vb6.exe        i386   10-Aug-2002   02:16:04    1,392,640   Msvbvm60.dll   i386   10-Aug-2002   02:10:22   1,695,744   Vba6.dll       i386				
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

Article ID: 327574 - Last Review: 02/27/2014 21:14:40 - Revision: 5.3

Microsoft Visual Basic 6.0 Enterprise Edition Service Pack 5

  • kbnosurvey kbarchive kbbug kbqfe kbpending KB327574
ERROR: at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited) at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)