If special characters are not shown correctly in the Windows client, it might be because the objects were compiled with the wrong code page.
To fix this you need to run C/Side with the unicode paramter:
<pre><code>finsql.exe unicode=1
</code></pre>Then open the relevant database and compile all objects.
Even though the characters might not be shown correctly inside C/Side the compilation will be done using unicode and the special characters will now be shown correctly in the client.

If special characters are not shown correctly in the Windows client, it might be because the objects were compiled with the wrong code page.

To fix this you need to run C/Side with the unicode paramter:

```
finsql.exe unicode=1
``` 

Then open the relevant database and compile all objects.

Even though the characters might not be shown correctly inside C/Side the compilation will be done using unicode and the special characters will now be shown correctly in the client.



Microsoft Dynamics 365 Business Central v14 and earlier

Special Characters in Translations

This blog is about development and automated testing for Dynamics 365 Business Central using Microsoft AL and Visual Studio Code.
You may also find a few posts about Dynamics NAV, C/Side and C/AL.
