Another French accent character problem

Grant

Sounds like a common problem, but I'm still searching for a solution, regarding French accent characters. I have already searched these forums for terms such as "Character Set", "Code Page", "Collation", etc - but no solutions that were evident for my situation (for example, I have downloaded and utilized the "Ansi2Ascii" and "Ascii2Ansi" functions. These work perfectly on my Navision installations, where I have a copy of the customer database. It also works on my SQL installation which was installed with all defaults recommended by Navision.

The problem comes where we have a Navision SQL installation running NA3.60. They have installed SQL with the following collation: SQL_Latin1_General_CP1_CI_AS. Using Enterprise Manager, it is possible to enter (for example) the character 'à'. It looks fine when viewed through SQL EM. However, when viewed through Navision, it is displayed as '...' (three dots). As a matter of fact, it does not seem possible to enter the 'à' character at all through Navision, as it always ends up appearing as '...'. (But from SQL EM, it shows up as 'à').

Any thoughts would be appreciated, I have to admit right now I'm thinking the only possible solution might be to re-install SQL, choose the standard installation options, and hope that a backup-restore works. The problem with this is that there is more than one SQL database involved, not all of them are Navision.
](*,)

kine

Which language you have set up in Control panels - Regional settings - Last page (Details?) - Language for non-Unicode applications??? Is there right settings? Because Navision is not unicode, he used this setting to translate characters on output and input, please, check this settings...

Grant

Hi Kine, thanks for your quick response - I finally got access to the system - the input locale on the Windows 2000 machine that SQL Server 2000 is installed on is English (United States). The other Input language that is installed but not set as default, is English (Canada). Looks pretty normal to me.

Grant

I figured it out, now that I had access to their system, and thanks to your comments about 'Collation'. Every text field of every Navision table had the "Collation" property (viewed from SQL 2000 Enterprise Manager, Design Table) set to a non-standard value of SQL_Latin1_General_CP437_BIN. The Navision database as a whole, had a standard collation of SQL_Latin1_General_CP1_CI_AS. I actually wrote a character-generator to see if there was any character which would display as the ‘à’ character, and stored these results in a new Navision table that I created. This helped determine what the real problem was.

As for why all of the Navision tables contained non-default collation properties, hopefully I get the real reason!