ACC: Linked SQL Server Binary Data Displayed Incorrectly (121834)
The information in this article applies to:
- Microsoft Access 1.0
- Microsoft Access 1.1
- Microsoft Access 2.0
- Microsoft Access for Windows 95 7.0
- Microsoft Access 97
This article was previously published under Q121834 SYMPTOMS
Advanced: Requires expert coding, interoperability, and multiuser skills.
When you link (attach) a 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 seems 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
Microsoft 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 to one of these binary fields, Microsoft Access
inserts ASCII characters, instead of binary data.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Access 1.0, 1.1,
2.0, 7.0 and 97.
REFERENCES
For more information about pass-through queries, search for "pass-through
queries, creating" and then "Send commands to an SQL database using a
pass-through query" using the Microsoft Access 97 Help Index.
For more information about SQL Server and Access, search for "SQL
databases," and then "Using the MSysConf table with linked SQL databases"
using the Microsoft Access 97 Help Index.
Modification Type: | Major | Last Reviewed: | 5/6/2003 |
---|
Keywords: | kbbug KB121834 |
---|
|