ACC2000: Linked SQL Server Binary Data Displayed Incorrectly (208900)
The information in this article applies to:
This article was previously published under Q208900 Advanced: Requires expert coding, interoperability, and multiuser skills.
This article applies only to a Microsoft Access database (.mdb).
SYMPTOMS
When you link a Microsoft SQL Server table that contains fields with Binary, Varbinary, or Timestamp data types, the data in these fields is displayed as seemingly random characters. Also, when you insert data from Microsoft Access into these fields in the SQL Server table, the data appears to consist of random characters.
CAUSE
Microsoft Access assumes that the data in the linked SQL Server table is
stored in ASCII format. However, the data in Binary, Varbinary, and
Timestamp fields is stored in binary format, not ASCII format. When
Access displays the data in these fields, it displays ASCII equivalents for the data in the fields, resulting in seemingly random characters being displayed.
When you try to insert data into one of these binary fields, Access
inserts ASCII characters instead of binary data.
STATUSMicrosoft has confirmed that this is a problem in Access. REFERENCESFor more information about pass-through queries, click Microsoft Access Help on the
Help menu, type send commands to an sql database using a pass-through query in the Office Assistant or
the Answer Wizard, and then click Search to view the topics
returned.
For more information about SQL Server and Access, click Microsoft Access Help on the Help menu, type use the msysconf table with linked sql databases in the Office Assistant or the Answer Wizard, and then click Search to view the topic.
Modification Type: | Minor | Last Reviewed: | 7/16/2004 |
---|
Keywords: | kbbug kbpending KB208900 |
---|
|