There are no Argentinian version of NAV. Actually there are no south American version. We are implementing several south American countries, and get the localization from local vars. We are using the US exe and Mexican language pack.
Ahmed Rashed Amini
Independent Consultant/Developer
There are no Argentinian version of NAV. Actually there are no south American version. We are implementing several south American countries, and get the localization from local vars. We are using the US exe and Mexican language pack.
We have a customer whose Chile office is looking to run Nav. We spoke to a Argentine company (Doversys) who do both Agrentina and Chile Localization for 5.0 SP1.
T
PS
There is no such thing as "Mexican" language, its Spanish.
(One of my ex-GF's was Venezuelan/French Canadian (yeah I know :-k ) and she would constantly freak out at me about S. America speaking Spanish and not Columbian or Mexican. I could always wind her up by telling her to go back o Mexico City, god she hated being referred to as Mexican )
There is no such thing as "Mexican" language, its Spanish.
The language layer for Mexico in NAV is referred to as ESM for "Spanish (Mexico)", as opposed to ESP for "Spanish (Spain, Traditional Sort)" for Spain itself. You can say it's the same language, but there are nuances that are different, just like there are nuances between the British version of English and the US version. (Labor vs Labour, Center vs Centre, things like that).
Another bit of trivia... the ENU language layer (for "English (United States)") in the W1 release is actually not the true ENU language layer. There are differences between the W1 version of ENU and actual ENU. They should really have a separate W1 language layer or maybe ENW for English Worldwide.
I agree with having a separate language for W1. In addition US changes all the (LCY) to ($) which makes comparing objects time consuming. I don't think they need to do this at all.
Or change the field to be captionclass and you would only modify CU 1 to grab either LCY or $
Ahmed Rashed Amini
Independent Consultant/Developer
Open the 400 db with a 400 SP3 client should activate the question.
The problem is that I opened the 4.00 SP1 database with the 4.00 SP3 client and I didn't get the question.
Is there a way the reinitiate the conversion?
I only want to do a technical upgrade because we have to much custom-made code. The reason for the techincal upgrade is that we have a lot of problems with the menusuite, which force us to remove the zup-file too often.
Open the 400 db with a 400 SP3 client should activate the question.
The problem is that I opened the 4.00 SP1 database with the 4.00 SP3 client and I didn't get the question.
Is there a way the reinitiate the conversion?
I only want http://wiki.dynamicsbook.com/index.php? ... al_upgrade
NAV technical upgrade - Dynamicsto do a technical upgrade because we have to much custom-made code. The reason for the techincal upgrade is that we have a lot of problems with the menusuite, which force us to remove the zup-file too often.
Comments
On the partnersite, you can find the upgradetoolkit you need to upgrade.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
I'd never had the question if I want to convert the database.....
Can some tell me how to initiate the conversion?
Maybe the Argentinian version of NAV is not available in 5.01.
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
We have a customer whose Chile office is looking to run Nav. We spoke to a Argentine company (Doversys) who do both Agrentina and Chile Localization for 5.0 SP1.
T
PS
There is no such thing as "Mexican" language, its Spanish.
(One of my ex-GF's was Venezuelan/French Canadian (yeah I know :-k ) and she would constantly freak out at me about S. America speaking Spanish and not Columbian or Mexican. I could always wind her up by telling her to go back o Mexico City, god she hated being referred to as Mexican )
Another bit of trivia... the ENU language layer (for "English (United States)") in the W1 release is actually not the true ENU language layer. There are differences between the W1 version of ENU and actual ENU. They should really have a separate W1 language layer or maybe ENW for English Worldwide.
RIS Plus, LLC
Or change the field to be captionclass and you would only modify CU 1 to grab either LCY or $
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n
The problem is that I opened the 4.00 SP1 database with the 4.00 SP3 client and I didn't get the question.
Is there a way the reinitiate the conversion?
I only want to do a technical upgrade because we have to much custom-made code. The reason for the techincal upgrade is that we have a lot of problems with the menusuite, which force us to remove the zup-file too often.
Here's a step by step from the Navision Wiki.
NAV technical upgrade - Dynamics