Results 1 to 2 of 2
  1. #1
    Join Date
    Apr 2017

    Unhappy Unanswered: secondary language problem - Access 2016

    I now have A2016. I downloaded the office language pack to include Hebrew language string processing. English is still the primary language. Nevertheless, when I open an existing working db (that was developed under Windows/Office XP, and has been working for over 10 years) with Hebrew strings, the Hebrew doesn't work. I checked the VBA, and the Hebrew characters that were there were turned to gibberish. I closed the db without saving changes, and re-opened it on another computer that has A2007 on it (the db is in a shared folder), and the Hebrew worked just fine.

    What's wrong with my A2016 and how can I fix it?

    Thanks so much in advance.


  2. #2
    Join Date
    Apr 2014
    Provided Answers: 32
    A2016 is soooo buggy. It could be the Access settings need set to UNICODE.
    Since it cannot see special characters.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts