MS Access query returning Chinese characters - possible table corruption?
I copied and pasted a new version of the data into my MS Access table and now I'm getting weird characters in my queries. Essentially if I say:
SELECT a, b from table1
everything is fine. If I instead do
SELECT a, b from table1 group by a, b
I get really weird characters as a result. At first I got upside down L's, but now I'm getting Chinese characters. It's weird because other queries in my database use the table and get the desired output. It seems like it's only when I do a group by that I have the problems. Any suggestions? I was ready to roll it out, but now I'm getting these errors!
This is a bug typically met if grouping on a memo field.
There may be several workarounds depending on your needs:
Select a, Left(b, 255) As b From table1 Group By a, Left(b, 255) Select a, Mid(b, 1) As b From table1 Group By a, Mid(b, 1) Select a, First(b) As firstb From table1 Group By a Select a, DLookUp("b","table1","Id = " & [table1]![Id] & "") AS b From table1 Group By a, DLookUp("b","table1","Id = " & [table1]![Id] & "")
“Chinese” characters getting inserted in one or more, MS Access query returning Chinese characters - possible table corruption? It's weird because other queries in my database use the table and get the desired� Now I get MS Access database engine does not recongnize '[Forms]![FrmDateRange]!BeginingDate]' as a valid field name or expression. So I included the field from the form on my query to see what it thought was in the text box and it shows nothing until I click on the field then it shows what looks like Chinese characters.
I have just had the same issue in various reports. The problem is indeed the Memo Field.
The solution that worked for me was more straight forward... I had to remove the "Group by" for the Memo field and the problem disapeared.
I realize this might not be an option in every situation, but if it is, this is the easiest solution as it requires no rewrite of the SQL or even any other change in the DB.
I found this solution here: Allen Brown - Grouping by Memo field yields garbage
Data corruption - chinese characters appearing., you may have to redesign the query or table structure. This can also happen when corruption has occured. hope this helps. The corruption is always found within the Prime table. Lately, I am often getting a single line of data in my access 2010 db coming up with a load of chinese characters. It has happened before, but lately it is becoming a regular occurrence and I would very much like it to stop.
Here is yet another option, which I just tried successfully. I was updating a query that someone else had created, and the author had included every field in the Group By clause, to return distinct records. I removed the entire Group By clause and inserted DISTINCT right after SELECT. No more Chinese. This may not be possible in some situations, but in this case it was a simple fix.
Also, I would not have thought of this if not for the insights offered above. Thanks everyone!
MS Access query returning Chinese characters, This is a mistake commonly encountered when grouping in the memo field. There may be several workarounds depending on your needs: Select a, Left(b, 255)� the query returns Chinese characters in all the text fields (they are set as long text) @Phil: Long text is the same thing as Memo - MS Access renamed the data type a while back.
After five months of no problems, I had this issue today on a group query which included a "Count" field, so the "DISTINCT" technique wouldn't work. What I did was wrap my LongText field around the offending field. In this table, all of the fields are ShortText except for "Description". So the field groups by CSTR([Description]) - and now it works fine! By the way - this came shortly after a MS Office 365 update!
Chinese Chars In Query Results, a table. A user tells me that it appears after they return to a record. Occasionaly I will get boxes and chinese characters in all but the Primary index field of a table. I have used queries before to remove corrupted records. Occasionaly I will get boxes and chinese characters in all but the Primary index field of a table. A user tells me that it appears after they return to a record that they have just recently edited. I have personally never seen the corruption appear, but as I "administer" the database I find it when I run maintenance on the table.
MS Access Corruption Notes, MS Access query returning Chinese characters. The best solution is to remove as many of the Long-Text fields as possible from the database. seems to me that the "DBO_" prefix shows up in SQL Server table field names. In a report in Access (11.65566.8821 SP2) I receive what appears to be Chinese characters for one field only. I can't find the setting that made that happen, I'd like to return that field to English.
Ask TOM "Differrent Character set and NLS", I have created a query on my main database table, and one field - a Memo Other queries return the same field without difficulty, so I don't Especially with memo fields, a single RECORD can be corrupted without affecting the rest. Every record displays a chinese character in the Memo field in question. I have created a query on my main database table, and one field - a Memo field - is returning Chinese looking characters in the query results. This happens only with this single query. Other queries return the same field without difficulty, so I don't believe the data itself is corrupt.
ms-access - MS Access查询返回汉字-可能损坏表吗？, Microsoft Access database files can become corrupted from time to time. There are a number of possible reasons for corruption, including network performance issues Could be due to a corrupted record in a table or control characters in a text field. Corrupted data will look like "chinese" characters in your data fields. Microsoft Access does not restrict the use of special characters such as a number sign (#), a period (.), or a quotation mark (") in the database object names or in the database field names. However, if you do use the special characters, you may experience unexpected errors.