Format command and .STX error

Dynamics 365 Business Central/NAV Developers Forum
#1

I have tested the 3 following statements:

  1. FormattedValue := FORMAT(SetField,0,1);
  2. FormattedValue := FORMAT(SetField,0,’<Standard Format,1>’);
  3. FORMAT(SetField,0,’’);

The value of SetField = 1.99.

I expect all 3 statements to return the same result.

Statement 1 works. Statements 2 & 3 return the following error:

"There are errors in the text conversion (text no. 102-2026 does not exist in the .stx file).

Internal error:47-1

I am running 4.0 SP1 (local DB). I am local admin and also tried replacing the fin.stx from CD.

#2

Firstly which language and country version are you using (The US is starting to get like Belgium and Switzerland these days, with all the language options, US, CA, FR, ES and with 2 countries, makes 8 versions.

First try using differnt language, then see if you can replicate this using W1 executables and STX.

Its almost impossible for the STX file to be corrupt, since it has a built in check sum, and would not allow you to start if it had an error. It could be though that you have mixed versions. EG SP1 STX with SP2 EXE.

Also check is 102-2026 exists in the stx file.

#3

Thanks for the reply.

I am running the US version. I will try a W1 version in the morning and let you know.

#4

Sorry, its not as simple as that, since the US version, now has 4 languages (ENC, ENU, ESM and FRC), and the issue could be with the language versions of the STX file being incomplete, or the wrong version. So its important to know which language and which version of STX you are using.

At first glace it looks like either a version mis match, eg, sp2 executable with sp1 STX file (generally the other way around is the same problem), or you have a bad language file in there somewhere.

A common issue is if you installed SP2 and SP1 onthe same machine, and some where the files are mixed up.

In any case my first suggestion would be to completely remove 4.00 SP1 (you don’t need it) and install SP2. SP2 Can access an SP1 database, so it will work cleaner that way.

#5

This is US 4.0 SP1 with language (ENU). SP2 has never been installed on this machine, but it may be a conflict with an earlier version.

#6

Hi all,

Don’t know if it could help, but I’ve got this kind of error after importing a fob done with a upper version that the one running on my side.