Several languages (codepages) on Navision database server

lzr

I read somewhere on forum that this won't work at all cause native database does not support it.

Microsoft says it can be problems, and therefore sql option should be used.

Anyone have any experience on this matter? I mean one database, several companies, where all companies have different languages.

ara3n

Hello I've done it for one client where they had US DB with Spain objects. The problem was that they had bough the Spain Spanish language pack. The Spanish Language pack does not have transaltion for US objects.

This is where the problem is. As long has the other companies don't use the objects from another country version you are OK.

What I had to do for this client was to load the Spanish Mexican inthe objects as well as the Spanish Spain and and change the Spanish Mexican to Spanish Spain.

Customer didn't want to pay extra for another langauge pack.
Sales people sell clients clouds sometimes.

gedas

Not really understood your problem, but....
Navision doesn't work with different codepages in one db. It is if russian from computer with cyrilic code page will add text to Navision, english man with another code page will see wrong characters.
So use SQL as you can set different code pages for different db. But different clients with different codepages can't see correct characters in the same database.

lzr

Ok, thanks for answer.

I guess they would all use the english objects (with translation to the different countries) and then users work in their own windows language.

The problem Microsoft spoke of was that there could be problems when making a backup. To me this sounds very dangerous.

How do you solve a multicodepage database with SQL? Just uncheck validate codepage and then choose a fitting collation? What if a user with another language than the one in the collation connects?

lzr

I understand they will see different characters if they are working in the same company but it should still work if you use native database?

russian client -> db1, company1
english client -> db1, company2

gedas

Yes, they will see....
But one database means the same sorting order for all companies in it and more trouble - the same uppercase converting table for all companies. This can get results when code fields values are converted from lower case fields (seach name) and this convertions is wrong. Because seach name is key field, navision goes crazy, get errors about database damages, you can't make backups, database tests and so.
Sorting order table and uppercase table is loaded from stx file during database creation and can't be changed later.
Regards

lzr

Aha ok, but if using SQL there will be no problem with having multiple companies with russian, english etc in the same database?

gedas

Yes.
You can set different code page for every database, so there will be no problems.
Just turn off "validate code page". This will allow connect to this database from client which has another code page. Or turn on (default) if you want to prevent do this.

gedas

Ups.
I read your question one more time and....
Code pages are set for databases but not for companies. In SQL server we can have many databases and many companies in every database. So companies in one database will have the same code page, but companies in different database can have different code pages.
The same asa in Native Navision.

kriki

gedas wrote:

The same asa in Native Navision.

For DB's and companies.
But the codepage cannot be choosen. It is always the same codepage.

lzr

Hmm. Ok, so if I understand it correctly the recommendation for 2 companies where one is russian and the other one is swedish is to have 2 databases and one company in each?

If I use one database and two companies it will still work with SQL but there could be a problem with the sorting since you can not choose "Swedish, Russian" as a collation?

lzr

I just spoke to Microsoft and if I choose "Caseless 3.4.1 database sort order, case-insensitive, accent-sensitive (49)" as a collation for SQL it is possible to use russian and swedish in the same databse. Now I have to try it out

Thank you for all input on this!