NAV/SQL language problem

marvinq
marvinq Member Posts: 69
edited 2011-02-19 in NAV Three Tier
Hi,

I just switched a SQL database for my NAV 2009.

An external .Net application is posting records to my NAV, but after changing the SQL I am stuck with a (for me) strange problem. The application is sending via a webservice to NAV with some parameters, but I get a problem with option fields...

Example: Type6 is an option-field defined in NAV like this..:

Data Type: Option
OptionString: Version,Update
OptionCaption: Version,Opdatering
OptionCaptionML: DAN=Version,Opdatering;ENU=Version,Update

In my application I have a line like this...:

temp = ""+Type6.Update

Before changing the SQL the accepted values for temp was naturally "Version" and "Update". Now all of a sudden it only accepts the danish translation "Version" and "Opdatering", which obviously gives me problems when choosing "Update".

Why is that? Why is my webservice/SQL suddenly asking for the translation instead for the actual option defined in NAV. Have I set some language parameters to my SQL database??

Please help!

Comments

  • marvinq
    marvinq Member Posts: 69
    Just made an observation :)

    I opened the RTC Client on the server and changed the display language (in the client) back to English, and restarted my webservice. And now it seems to work.

    Can anyone clarify if there is an connection between the RTC Client language on the server and the valid input variables in the webservice. There must be some connection, but changing the RTC Client language, do this really affect the language for other applications consuming the webservice???

    And what happens if I distribute my application to other computers where the RTC language is Danish? Will this give me the same error??

Categories