Microsoft KB Archive/883576

= FIX: You receive incorrect results when you use strings that have more than two characters to define a range, and then you access data in a SQL Server CE OLE DB application =

Article ID: 883576

Article Last Modified on 3/23/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Windows CE Edition 2.0
 * Microsoft SQL Server 2000 Windows CE Edition 1.1

-



BUG #: 10011 (SSCE)



Contents

 * Summary
 * Symptoms
 * Cause
 * Resolution
 * Hotfix information
 * Prerequisites
 * Restart information
 * Hotfix file information
 * Status
 * More Information
 * References



SUMMARY
This article contains the following information about this hotfix release:
 * The issues that this hotfix package fixes
 * The prerequisites for installing the hotfix package
 * Requirements for restarting your computer after you install the hotfix package
 * A step-by-step procedure that explains how to apply this hotfix
 * The files that the hotfix package contains

back to the top



SYMPTOMS
A Microsoft SQL Server 2000 Windows CE Edition (SQL Server CE) OLE DB application returns results that are not correct when you define a range to restrict the range of rows that you access from a table and then you access data from the table. Also, when you verify the results, you can see that the first two characters of the string values are used to define the range.

This problem occurs if the following conditions are true:
 * You use strings that have more than two characters to define the range.
 * You bind the range data string as the DBTYPE_WSTR OLE DB data type.
 * You use the SetRange method of the IRowSetIndex interface to restrict the range of rows that you access.

back to the top



CAUSE
The OLE DB Provider for SQL Server CE cannot detect the DBTYPE_WSTR OLE DB data type that the SQL Server CE OLE DB application passes. Therefore, the OLE DB Provider for SQL Server CE uses the fixed length of 4 bytes to bind data. The length of 4 bytes is two characters in the WCHAR data type.

back to the top



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

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;[LN;CNTACTMS]

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.

back to the top

Prerequisites
This hotfix requires Microsoft SQL Server 2000 Windows CE Edition 1.1 or Microsoft SQL Server 2000 Windows CE Edition 2.0.

back to the top

Restart information
You do not have to restart your computer after you apply this hotfix.

back to the top

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) 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.

SQL Server 2000 Windows CE Edition 1.1
Date        Time   Version            Size    File name --  08-Jun-2001  12:36                      5,191  Dllregister.exe  ARM 12-Jul-2004 09:25  1.1.6712.0      1,258,562  Ssce10.dll       ARM

SQL Server 2000 Windows CE Edition 2.0
  Date         Time   Version            Size    File name --  15-Aug-2002  18:03                      5,193  Dllregister.exe  ARM 02-Jul-2004 12:49  2.0.6702.0      1,405,508  Ssce20.dll       ARM 07-May-2004 15:26  2.0.6507.0        264,774  Ssceca20.dll     ARM 07-May-2004 15:20  2.0.6507.0        221,250  Sscesa20.dll     x86 Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.back to the top



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.

back to the top



SQL Server 2000 Windows CE Edition 1.1
If SQL Server 2000 Windows CE Edition 1.1 is running on your device or computer, follow these steps to apply the hotfix:
 * 1) Locate the existing SQL Server CE 1.0 installation folder on the Windows CE-based device, and then replace the Ssce10.dll file in the folder. The Ssce10.dll file is the SQL Server CE Engine file.

Note
 * 1) * If you deploy your SQL Server CE OLE DB application from Microsoft Visual Studio .NET, the SQL Server CE files are installed in the \Windows\Sqlce 2.0 folder.
 * 2) * If you deploy your SQL Server CE OLE DB application from Microsoft eMbedded Visual Tools, the SQL Server CE files are installed in the \Windows folder.
 * 3) * When you develop an application in a mixed environment that contains Visual Studio .NET and eMbedded Visual Tools, we recommend that you replace the files in both the folders. In practice, however, you can just replace the files in the folder where the application was last deployed.
 * 4) Copy the Dllregister.exe file to the folder where the SQL Server CE files are installed on the Windows CE-based device.
 * 5) Run the Dllregister.exe file to register the Ssce10.dll file on the Windows CE-based device.
 * 6) Perform a soft reset on the Windows CE-based device.

SQL Server 2000 Windows CE Edition 2.0
If SQL Server 2000 Windows CE Edition 2.0 is running on your device or computer, follow these steps to apply the hotfix:  Locate the existing SQL Server CE 2.0 installation folder on the Windows CE-based device, and then replace the following files in the folder:  Ssce20.dll (SQL Server CE Engine) Ssceca20.dll (SQL Server CE Client Agent)</li></ul>

Note <ul> If you deploy your SQL Server CE OLE DB application from Microsoft Visual Studio .NET, the SQL Server CE files are installed in the \Windows\Sqlce 2.0 folder.</li> If you deploy your SQL Server CE OLE DB application from Microsoft eMbedded Visual Tools, the SQL Server CE files are installed in the \Windows folder.</li> If you develop an application in a mixed environment that contains Visual Studio .NET and eMbedded Visual Tools, it is a best practice to replace the files in both the folders. In a typical situation, however, you can replace the files in the folder where the application was last deployed.</li></ul> </li> Copy the Dllregister.exe file to the folder where the SQL Server CE files are installed on the Windows CE-based device.</li> Run the Dllregister.exe file to register the Ssce20.dll file and the Ssceca20.dll file on the Windows CE-based device.</li> Perform a soft reset on the Windows CE-based device.</li> On the computer that is running Microsoft Internet Information Services (IIS), replace the Sscesa20.dll (SQL Server CE Server Agent) file in the appropriate virtual directory.</li> Restart IIS on the computer that is running IIS. To do this, run the iisreset command at a command prompt.</li></ol>

back to the top

<div class="references_section">