Options

Cannot enter "á" into NAV2009 R2 classic client on SQL

ichladilichladil Member Posts: 68
Hello,

I have a classic client NAV 2009 R2 (Build 32012). As I am from the Czech Republic I need to use the accented characters. NAV client accepts all of the accented characters like ěščřžý except for accented á. I cannot write á directly, however I can copy and paste it to the client. We have tested this issue on 3 machines (Windows 7, Windows Server 2003). It doesn't work even in the "system dialogs" like create new database, where I would expect no issues. It doesn't work however in classic client on SQL only - it works in classic client with native DB and in RTC client.

I would welcome any thoughts on what may cause this issue?

Thanks

Igor

Comments

  • Options
    kinekine Member Posts: 12,562
    Hello Igor,

    one basic question - which language is set in local settings for Non-unicode applications on the windows? Is it Czech?

    second question - which collation you are using on the database?

    (jsem si jistý že někdo z kolegů by poradil... :-))
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Options
    ichladilichladil Member Posts: 68
    Thanks Kine! It wasn't actually caused by the code page/collations. I had another SQL NAV DB with the same settings and that one worked. However after several unsuccessful attempts to make it working I have made a Navision Backup/Restore to the new SQL DB and it has started to work - with all of the things setup in the same way as in the original DB. (Restart works as usually ...)

    Igor
  • Options
    kinekine Member Posts: 12,562
    Than question is, if the problem was "entering" the character, or "already entered" characters... :-) when you restored NAV backup on PC with different local settings, it will mess the characters because "re-coding" between local and target codepages...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Options
    ichladilichladil Member Posts: 68
    The problem was with the "entering" the character. For the characters already in DB I understand that backup/restore may change the things. But I didn't understand why it helped for my issues with "entering" the character.
  • Options
    kinekine Member Posts: 12,562
    Than may be the difference is somewhere in data in table $ndo$dbproperty which could have some effect to this...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Options
    GreenSunGreenSun Member Posts: 1
    @ichladil I have exactly the same problem with that character. Do you found a solution for this behavior?
    Every tipp how to solve that is appreciated!
Sign In or Register to comment.