No answers for this for this? I work with a DB where the ID fields are always stored as binary so linking a table. In past versions of Access I recall finding a work-around for this but I can't seem to locate those instructions on the webs
Access 2013 - Linked Table to SQL Server - Binary Data Displays as Asian/Chinese Characters
I have a SQL Server 2012 database (standard, not express). When I create an ODBC connection to the database and link the tables, binary columns/fields are being displayed as what appears to be Asian characters. The data appears correctly in SQL Server Management Studio and retrieves properly in Visual Studio using System.Data.SqlClient.
The data looks like this is SQL Server Management Studio (look at columns: PasswordHash and PasswordSalt):
The same data looks like this in MS Access 2013:
Why is MS Access incorrectly changing the correlation of binary data so it looks like Asian characters? The encoding in the database is: SQL_Latin1_General_CP1_CI_AS
Microsoft 365 and Office | Access | For home | Windows
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
8 answers
Sort by: Most helpful
-
Anonymous
2014-09-29T20:49:10+00:00 -
Anonymous
2014-09-30T00:01:55+00:00 Only thing I can add to the discussion, not a resolution nor a workaround, is the confirmation that Microsoft confirmed this issue way back in the days as a bug.
http://support2.microsoft.com/kb/121834
Not sure if Microsoft ever came up with a solution for this.
I know if text is stored in Binary field, you may convert this to a String.
-
Anonymous
2014-09-30T06:32:31+00:00 There was no real resolution. I solved this problem by dropping Access as a solution and using Visual Studio. It is ridiculous how bad support is on solving issues. It should be impossible for any solution to auto-change languages and its a substantial flaw to ignore actual encoding.
I should thank Steve Ballmer (worst and most incompetent CEO ever) for the typical response that is embedded deeply within all MS employees.
PLEASE NOTE: I cannot and do not blame actual employees as it is clear that their responses were planned and forced.
The typical MS employee response (as forced by Steve Ballmer): Your problem is not a problem it works that way, "by design".... "by design" means we programmed it, it does whatever it does, right or wrong, good or bad, and you should be happy with it. Please, don't bother us with how our products "should work", or whether you are happy or not happy with our product. Wait until the next release where we will tell you what is better for you.
If I thought I someone at MS was even allowed to fix these problems, I would help. Please close/delete/forget this issue as it was never going to be resolved anyway.