• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 413
  • Last Modified:

Asian characters in query field name in Access 2010

This morning I tried to run an Access 2010 query I made a few weeks ago and it prompted me for…. Well I don’t know since I can’t read Japanese, Korean or Chinese or whatever language it used.  Looking at the query in design view shows the field name is now in some Asian language.  All of the fields in the table still show their English names but in the designer one field is now called “[¿¿¿$¿¿¿$]” – hence the prompt for a parameter - the other fields in the designer still have their English names.  The query is based on one table – MsysObjects – and it only uses 5 of the fields – I don’t remember which field is being translated although it was not one of the “OLE Object” types.
I have seen this automatic translation to an Asian language in Access data before but never in a field or other object name.  I never found out what was changing data from English to whatever Asian language it was using although the problem was more frequent if I imported data from FoxPro tables.  It also happened sometimes when multiple users were using the same Access DB.  I started using adp projects for multi-user databases and haven’t had the problem with any of those.
I don’t make adp projects anymore since it seems like they are going to be dropping support for these in the near future.  The DB I am having the problem with now is an Access 2010 accdb type.  I have done multiple compact and repairs and like the problem with the Asian data it doesn’t help a bit.  I am using Windows 7 Pro on a 64 bit machine although our IS department installed the 32 bit version of Windows. The Office 2010 version is also 32 bit.
Can someone please tell me why Access does this and how to stop it?
Thanks
 Picture of query in design view
0
thresholds
Asked:
thresholds
  • 7
  • 6
  • 2
1 Solution
 
MINDSUPERBCommented:
Have a try to do a compact and repair. It might helps.

Sincerely,
Ed
0
 
MINDSUPERBCommented:
Sorry, I missed the your sentence that you have already did the the compact and repair.

Ed
0
 
Rey Obrero (Capricorn1)Commented:

i would create a new blank db and import all the objects.

most probable is that the msysobjects table is corrupted.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
thresholdsAuthor Commented:
I just started making a new DB and importing the objects - except the problematic one.  I'd still like to know how this happens since it seems to be a recurring problem - although like I said this is the first time I've seen this with object names instead of data.
0
 
Rey Obrero (Capricorn1)Commented:
<except the problematic one>  which table is this?

<...how this happens since it seems to be a recurring problem>
how often?
0
 
thresholdsAuthor Commented:
The object I am not importing is the query based on MsysObjects and of course I am not importing the system tables.  I've never had this problem with object names before but have seen it several times where data has been 'translated' into Chinese or whatever.  It's been a couple of years since I've seen the problem with the data since I stopped importing Foxpro tables and I started using adp projects for multi-user databases.  The system I am using now is brand new as of a few months ago and this is the first time I’ve had this problem with the new PC.
I think I had the data problem with Access 2007 but it may have been the 2003 version.
0
 
Rey Obrero (Capricorn1)Commented:
just make sure that your Access/Office version have the latest SP
0
 
thresholdsAuthor Commented:
Our IS department does that since they want to make sure everyone is using the same version.  I did check for updates and no service packs are listed for Office 2010 - just a few security updates.
0
 
Rey Obrero (Capricorn1)Commented:
i've been using the same kind of query you were using, for years,  and never had any problem with it
0
 
thresholdsAuthor Commented:
I've always said I have a magnetic personality - maybe that's the problem.  Maybe I should get a job as a bug tester - if there's one there I'll find it.
0
 
Rey Obrero (Capricorn1)Commented:
or you can set the level of your threshold error to a higher value
0
 
thresholdsAuthor Commented:
You are correct in that the problem is not a deal breaker but if it pops up somewhere else it might be.  So far the new DB I made is working fine although I didn't bring in the query I was having trouble with and I left the system objects hidden.
0
 
Rey Obrero (Capricorn1)Commented:
i remember, there was a case when a query is really returning weird results i have to delete the query, then did a compact and repair of the db.

created a new query with the same structure as the the one deleted and the query ran smoothly with the correct results.
0
 
thresholdsAuthor Commented:
I am going to close this question as no real solution seems to be available.  Apparently Access database corruption isn't as unusual as it should be.
0
 
thresholdsAuthor Commented:
Access DBs get corrupted too much.
0

Featured Post

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

  • 7
  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now