Text export - Differences 3.70 // 4.00

toenne

:shock: I'm trying to compare 370's und 400's objects as text exports. Although both installed versions are switched to german language the output of 370 differs from the 400 in following details:

Navision 4.00
OBJECT-PROPERTIES
{
Date=08.06.01;
Time=12:00:00;
Version List=NAVW13.00;
}
...
NotBlank=Yes
...

Navision 3.70
OBJECT-PROPERTIES
{
Datum=08.06.01;
Zeit=12:00:00;
Versions Liste=NAVW13.00;
}
...
NotBlank=Ja
...

Is this a bug or is it fixable by configuration??
anybody anyidea? :roll:

Luc_VanDyck

Try switching to English when exporting the objects in 3.70. Or open your 3.70 database with W1 3.70 and export the objects with this version.

kine

It is based on fin.stx in Client folder. Copy correct fin.stx from DEU or ENG into client folder and try again...

Sorcerer

the fin.stx does not solve this problem....
as you can see in the object designer the shortcut for design is now on the d and not as before on the e.
it seems that the german ntc has forgotten some localisation...as seen before in version 3.01a same procedure as every major release....

kine

the fin.stx solve the problem of used localization in text import and export of objects. If you have fin.stx from DEU folder in client folder, text objects will be localized. If you use the fin.stx from ENU folder, the text objects will be english.

RobertMo

Exactly as Kine says.
But it is not enough that you change language within application. You should copy the file(s) manually.

BTW. Which fin.stx (and fin.etx) is located directly in client folder and thus defines "the more default" language depends on instlation CD. When MS country companies are preparing instalation CD for their country they already put the "local" versions of fin.stx and fin.etx in Client folder...

you can guess the rest...

RobertMo

That's why most developers have more "language versions" of same Navision version installed, like:
C:\Program Files\Navision Attain W1 360\...
C:\Program Files\Navision Attain SI 360\...
C:\Program Files\Navision Attain DE 360\...
etc.

Sorcerer

even if the fin.stx is copied from the deu folder the file is in english....
at least in version 19365....

ngebhard

May this as well be the reason that the values of properties changed to English comparing to the V3.70? I thought MBS just won't translate things like this any more. Maybe I should have a try (even if this is not a real problem )..

Regards,
N. Gebhard

RobertMo

ngebhard wrote:

... the values of properties changed to English comparing to the V3.70...

you had also values of properties translated ? which one (beside Yes/No)?

BTW, if 4.00 export is always in ENU, then try exporting 3.70 in ENU as well...

NaviTools.com

Hi,

Try using Navision Developers Toolkit 2.0. One of new features is that you can select .stx file in Import window.

Or just open one of your files in text editor and do Find/Replace of those four strings (this worked well from v1.0 ).