Home | Forums | Contact | Search | Syndication  
 [login] [create account]   Saturday, May 25, 2024 
Setting up a Multi-Byte Environment for SalesLogix  
Description:  Setting up a multi-byte environment for SalesLogix is a fairly simple process, but there are some items to take into consideration for a sound deployment on a global basis.

Category:  SalesLogix Administration
Author:  Matt Dockins
Submitted:  2/29/2008
Article has been read 24450 times

Rating: - 4.5 out of 5 by 22 users

Setting up a Multi-Byte Environment for SalesLogix

Setting up a multi-byte environment for SalesLogix is a fairly simple process, but there are some items to take into consideration for a sound deployment on a global basis.

First, lets set up the environment to allow multi-byte languages.

Step 1: Insure the Connection Manager connection on the server has the Auto Translate property disabled, as follows:
  • open Connection Manager on the SLX Server
  • select the database connection and Edit
  • click the All tab and double-click the Auto Translate field
  • select False, then OK to close. Save settings and exit connection manager
  • Note: server must be restarted to enable the change.

Step 2: On the host database insure the collation on the host should be SQL_Latin1_General_CP1_CI_AS. By default, this is collation of the databases shipped on the SalesLogix CD - they will retain that configuration when attached to a SQL server.

Step 3: LAN Client configuration - In order for a client to properly insert and display multi-byte characters, the client must use both regional and language settings appropriate for that language. In Control Panel | Regional Settings, the Standards and Formats must be set to <language>:

And under the Advanced tab the setting for non-unicode programs must be set to <language> also, as follows:

Step 4: Remote Client configuration - when SLX creates a remote user database, a collation type is not explicitly set. As mentioned above, if the host database was attached off of a SLX CD the collation on the host should already be SQL_Latin1_General_CP1_CI_AS. When cutting a remote you must use a SQL instance using this as the default collation type, allowing the remote and the host to have the same collation type. To specify which server you cut against you can use the middle option in the top right radio group of the Create Database Options dialog.

Instances of MSDE installed by versions of SalesLogix prior to v7.0 do NOT force this collation type. Starting with v7.0 all MSDE instances installed by SalesLogix DO force this collation type.

Step 5: Sync Server - If the sync server is installed on a machine whose operating system does not by default support multi-byte characters (i.e. English), then the regional and language options must be set as above (for LAN client) to provide multi-byte language support.

Step 6: Localization - To Localize a client, the following files must be present in the Program Files\SalesLogix folder:
  • SalesLogix.mld - this is the dictionary file, and contains the translated strings appropriate for the language being localized to.
  • SalesLogixINTL.ini - a text file listing the SLX applications to be translated at runtime.
  • SLXIntForms.slx - a text file containing the resize data which is used by the applications at runtime
  • SLXTranslator.dll - contains supporting code for localization functions.
There is no install for these files - they can be simply copied to the client machines as required.

Enabling Cross-Language Capability in the Client

Some operating systems will not permit the LAN client to properly display and save character sets in a different language. For example, on a German operating system the LAN client will not correctly commit Greek characters to the database. This can be corrected by using the client localization capability - setup details are as follows:
  • Connection Manager must be set to disable the Auto Translate property, as described above.
  • On the LAN client the regional settings (both Regional Options and Advanced, as illustrated above) must be set to the language to be used; in our example above, Greek.
  • Use the SalesLogix localization tool (SLXLocal.exe) to create a dictionary with a language column but no translations, as follows:
    • Start SLXLocal.exe
    • Create a new project - use any name
    • Project | Add EXE or DLL - select SalesLogix.exe
    • Add your desired language under Edit | Add Language (Greek, in our example above)
    • Project | Languages - make sure your desired language (Greek) is selected
    • File | Generate Dictionary - dictionary can be saved with any name (ending in .mld extension) but must be renamed to SalesLogix.mld for use with the client.
  • On LAN client, two of the four localization files must be copied into the \SalesLogix folder. As listed above, the files are SalesLogix.mld and SalesLogixINTL.ini. The resize file (SLXIntForms.slx) and translator dll are not required in this case, as you are not actually translating the client.
  • If the client still doesn’t display characters as desired, the machine may need to be rebooted.
* Much of the excerpt above comes from a document titled “Setting up a multibyte SLX Environment” authored by bdonison.


Below is an example of how the multi-byte language translation works

The Localized Client (Korean)

Korean Note History

The Same Record utilizing the Chinese Code Page (the Korean characters appear to have been translated character by character – in other words, what might have been entered as “The Quick Brown Fox Jumped Over the Lazy Dog” in Korean might say “OIYDO:HOXDCJNUWHUHW(PIUP” in Chinese. A concern is that this translated character might contain profanity or slander or some other miscommunication.

The Same record with multibyte code pages removed (English only)

The raw data in SQL Server

* Note, double byte characters consume twice the space of single byte characters – this means that a field with a length of 10 characters will only hold 5 multibyte characters.

* Note, since you can only have one active code page per machine that SalesLogix can access, for citrix and terminal server deployments it could mean that one citrix or terminal server may be necessary per localized multi-byte language.

About the Author

  Matt Dockins
(SalesLogix Business Partner)
Premier Programming Services, LLC

Matt Dockins is the president of Premier Programming Services, LLC. With 8 years of experience working in SalesLogix from version 5.7 through 7.5. Matt has developed a number of customizations and external applications for SalesLogix and has been responsible for the design and implementation of a large number of high ROI projects (one of which acheived an 1193% ROI in just 2 years).

Premier Programming Services is a Sage Development Partner, Microsoft ISV, and VineyardSoft KnowledgeSync Partner.
- http://www.premierprogrammingservices.com

View online profile for Matt Dockins

[ back to top] [ send to a friend]  

Rate This Article you must log-in to rate articles. [login here] 
Please log in to rate article.

Comments & Discussion you must log-in to add comments. [login here] 
Author Article Comments and Discussion
Eckart Fischer

Re: Setting up a Multi-Byte Environment for SalesLogix
Posted: 2/19/2009 8:15:10 AM
Great documentation! Very helpful for our SLX implementation in Japan!
One question: do you have any experience with a Japanese mld? We have one implemented, but SLX (6.2.6) adds not only shortcuts at the end of menu items (which is OK), but also right in the middle of the item (which doesn't look well because it's a latin letter within the Japanese phrase.

This is probably a Windows setting, but I don't have a clue where to change it. On the remote machines we have Japanese Windows XP installed.

Any comment would be appreciated.

Best regards from the Black Forest/Germany.
Snow Monkey

Re: Setting up a Multi-Byte Environment for SalesLogix
Posted: 5/19/2010 3:28:42 PM
Matt , where will i get slxlocal.exe?
Matt Dockins

Re: Setting up a Multi-Byte Environment for SalesLogix
Posted: 5/31/2010 3:47:55 PM
You can download slxlocal.exe as part of the localization toolkit, which is available from the Sage SalesLogix FTP site.

       Visit the slxdeveloper.com Community Forums!
Not finding the information you need here? Try the forums! Get help from others in the community, share your expertise, get what you need from the slxdeveloper.com community. Go to the forums...

 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
page cache (param): 5/25/2024 8:30:39 AM