In support, we often get questions about Multilingual installations of Microsoft Dynamics GP.

While it’s possible to use Microsoft Dynamics GP in a Multilingual Installation environment, there are some important things to keep in mind.

Here are Frequently Asked Questions about Multilingual Installs for Microsoft Dynamics GP:

Question 1: What is a Multilingual Installation?

Answer 1: A Multilingual Installation is an environment in which multiple language release installations (unique language code folders) share the same DYNAMICS database, and potentially the same company databases.

Each unique release contains specific words and phrases to match the language of that country. As an example, the United Kingdom installation uses "cheque" instead of "check." There are 27 unique languages to choose from when you install Microsoft Dynamics GP:

Andean Argentina Australia Austria Belgium Canada Chile
China France Germany Hong Kong Indonesia Japan Latin America
Luxembourg Malaysia Middle East Netherlands New Zealand Philippines Singapore
South Africa Spain Taiwan Thailand United Kingdom and Ireland United States

-

Question 2: How should I install the code, and create my companies in a Multilingual environment?

Answer 2: In a nutshell: The DYNAMICS database, and all company databases should be created/installed/upgraded using one PRIMARY language code folder only!

Click HERE for more detail around how to successfully install the DYNAMICS and Company databases in a Multilingual environment.

Question 3: Does it REALLY matter ‘how’ I install my companies in a Multilingual Installation environment?

Answer 3: YES!!!! IF the DYNAMICS and Company databases are not installed/created/upgraded correctly you will run into problems down the road (errors associated with audit trail codes, and/or problems closing the year in General Ledger).

While different country code installations (unique language code folders) can be used to connect to the same company database within a SQL instance: ALL company databases that are located on the same SQL instance should be created/upgraded using the same Primary Code Folder. This is because Audit Trail codes must match across all company databases within the same SQL instance.

Question 4: What if I accidentally upgraded one of my companies with the secondary code folder on accident?

Answer 4: If you accidentally upgraded/installed a company database with the secondary code folder, the following may occur:

  • You may receive the error message, “Violation of PRIMARY KEY constraint 'PKSY40100', Cannot insert duplicate key in object 'dbo.SY40100'” when you attempt to create a new fiscal year (Microsoft Dynamics GP >> Tools >> Setup >> Company >> Fiscal Periods).

  • When you try to close the year in General Ledger, nothing happens (because the audit trail codes between DYNAMICS..MESSAGES and the SY01000 are no longer in synch).

Click HERE for detailed information around how to re-synchronize the audit trail codes for company databases that were incorrectly installed/upgraded with the secondary code folder.

For additional information, see KB Article 887108, “Answers to frequently asked questions about international installations of Microsoft Dynamics GP”.

I hope this information is helpful!