Microsoft KB Archive/269444

= ACC2000: #Deleted Entries Appear in Alternate Rows in Linked SQL Server Tables =

Article ID: 269444

Article Last Modified on 6/28/2004

-

APPLIES TO


 * Microsoft Access 2000 Standard Edition

-



This article was previously published under Q269444



Moderate: Requires basic macro, coding, and interoperability skills.

This article applies only to a Microsoft Access database (.mdb).



SYMPTOMS
In a linked table from Microsoft SQL Server 6.5, Microsoft SQL Server 7.0, or Microsoft Data Engine (MSDE) you see #Deleted in alternate rows. One row has the typical data, the next contains #Deleted entries, the next typical data, and so on.



CAUSE
This behavior can occur under the following conditions:
 * The table has numeric or text field columns.
 * The SQL Server database has been created on a server with non-default code pages and sort order.
 * The version of the Microsoft ODBC SQL Server driver accessing the table is 3.70.0623.

NOTE: This problem does not occur with earlier or later versions of the Microsoft ODBC SQL Server driver.



RESOLUTION
To resolve this problem, do one of the following:  When you configure the data source name (DSN) in the ODBC Administrator, on the last page, clear the Perform translation for character data option. Create a pass-through query in Access instead of using linked tables.

NOTE: This only works if the data can be read-only. Install a newer SQL Server ODBC driver by installing the latest version of Microsoft Data Access Components (MDAC). For more information about the latest version of MDAC and to download it, please visit the following Microsoft Web site:

http://msdn.microsoft.com/dataaccess





STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



Steps to Reproduce the Behavior
 On a clean Microsoft Windows NT Server or Microsoft Windows 2000 Server computer, start Setup of SQL Server 7.0.</li> In the Setup Type dialog box, click Custom, and then click Next.</li> In the Select Components dialog box, click Next.</li> In the Character Set/Sort Order/Unicode Collation dialog box, set the following items:  Click Character Set, and then click 437 US English.</li> Click Sort Order, and then click Binary Order.</li> Make sure Locale Identifier is set to Binary Order.</li> Of the check boxes on the lower right, verify that Case-insensitive is the only item selected.</li></ul>

</li> Complete the Setup of SQL Server, and then restart the computer.</li> On another computer that is running a clean installation of Microsoft Windows 95 or Microsoft Windows 98, install Access 2000.</li> With the ODBC Administrator, create a system data source name (DSN) for SQL Server 7.0, keeping the default settings, and specifying the Pubs sample database as the default database to connect to on the server.</li> In Microsoft Access 2000, link the Publishers and Pub_Info tables through the DSN that you created in the previous step.</li> Open the linked tables. Note that #Deleted appears in alternate rows as described in the &quot;Symptoms&quot; section.</li> Create a SQL specific pass-through query with the same DSN, and then run either of the following SQL statements:

Select * from publishers

-or

Select * from pub_info

Note that the data is returned correctly, unlike the data in the linked tables.</li> Quit Access.</li> <li>Open the ODBC Administrator, and then reconfigure the system DSN so that the Perform translation for character data option check box is not selected (the check box is selected by default).</li> <li>Start Access again, and create links to two other Pubs tables. Note that the data is now displayed correctly.</li></ol>

<div class="references_section">