Weird nas problem - 'Ja' is not an option

Magno

Hi,

We installed an NAS, but when we try to start it, it gives following error:

'Ja' is not an option.

The existing options are:

No, Yes

When i log on to navision with the same user id, and change the language, i does work, The weird thing is, the NAS runned before, but suddenly it does this.

Does anyone know how we can avoid this?

ta5

Maybe NAS is using the same zup as the normal Navision-Client located on the same machine?

Anyway, I've seen this message a couple of times with normal Navision-Client when changing Language back and forth.

Thomas

Magno

i think it has probably something to do with option language, but it surprises me, the option doesn't change his checks when in another language...

kriki

In the optionstring for the NAS (and this is also for the clients), use 0/1 and not No/Yes or Nee/Ja or Non/Oui or Nein/Ja or No/Sì or Ie/Hai.
Did I forget some language?

kine

kriki wrote:

In the optionstring for the NAS (and this is also for the clients), use 0/1 and not No/Yes or Nee/Ja or Non/Oui or Nein/Ja or No/Sì or Ie/Hai.
Did I forget some language?

Yes, czech... Ne/Ano :whistle:

masch

try to copy the files fin.stx and fin.etx from a working client directory to the directory where the NAS is installed and restart the NAS.

Phenno

This is interesting...
Which language is used by default on NAS?
From stx or English?

Phenno

kine wrote:

kriki wrote:

In the optionstring for the NAS (and this is also for the clients), use 0/1 and not No/Yes or Nee/Ja or Non/Oui or Nein/Ja or No/Sì or Ie/Hai.
Did I forget some language?

Yes, czech... Ne/Ano :whistle:

Oh no... not again (Ne/Da :whistle: )

kine

Phenno wrote:

This is interesting...
Which language is used by default on NAS?
From stx or English?

Sometimes I wonder which one, because it seems that sometime one and another time other...

But the application default language depends on CU1 function ApplicationLanguage. This function is called each time the application wants to know the default language. But I am not sure, if the default language is set before calling NASHandler or after that. Because if it is called after, it means that everything in NASHandler will be in English but everything called after that (through timer or other triggers) will be in default app language...

fufikk

Language can also be set programatically using for example
GLOBALLANGUAGE function.

This may be quite usefull if your application makes use of SETVIEW function on record. As far as I know this function is a neat way of filtering a record with parameter (passed to setview). The only problem is, that instead of field names it uses captions... and these are language dependend.[/code]

ajhvdb

Set and Getview can be used also with the parameter "UseNames"

fufikk

I think that UseNames only applies to GETVIEW. According to manual:

SETVIEW (Record)
Use this function to set the current sort order, key and filters on a table.

Record.SETVIEW(String)

but GETVIEW:

GETVIEW (Record)
Use this function to return a string that describes the current sort order, key and filters on a table.

String := Record.GETVIEW([UseNames])

or maybe I'm missing something...

Ruud

Hi,
I had the same problem and solved it like this:

Start Navision Client.
Change the language to English.
Close Navision.
Start the NAS. The nas wil now run correctly.
You can start Navision again and change the language if you like.
The Nas will continue.

Maybe it's possible to configure NAS having its own Zupfile ?

st0328

i am having the same problem with the Report. we are not working with NAS.


Here we are working for client. we have two languages

1) ENU
2) DEU

with ENU the report is working fine .

when the changed the language to DEU in RTC and tried to run the same report.
the below error is coming..

---

Microsoft Dynamics NAV Classic

---

Die Wahlmöglichkeit 'Yes' ist nicht vorhanden.

Die Wahlmöglichkeiten sind:

Nein, Ja

---

OK

---

please suggest me to solve this..

GRIZZLY

Try to investigate your code and find line (or turn on the debugger):
SETRANGE("Boolean Field", Yes)

When the language is ENU it doesn't matter, but when you change to another language an error occures.

davorp

I just had similar problem. Opening native local database with NAV 6.0 classic client gave the error:

'Da' is not an option.
The existing options are:
No, Yes

It was not possible to open local 6.0 DB any which way I tried. ](*,)

In the end, it turns out that I had another NAV 5.0 client with another native local database opened at the same time. Closing NAV 5.0 client allowed NAV 2009 to open its own local database without problem. Go figure...
Usually one would expect this sort of behavior (not being allowed to open another database) when you run the same NAV client twice but not with different fin.exe files/versions.

tinoruijs

Ok. Encountered this problem today.
Tried all the suggestions given here, but nothing worked.
I made a copy of the client directory and used the fin.exe. Still the error occurced.
The solution in my case was to delete the directory NLD from copied directory in Program Files. Then started fin.exe and the language was automaticly English.
So problem solved. \:D/