hi all, we have an implementation of navision running under sql. we install sql server in two servers, one for store “real” data an another one to manage copies, make tests for developments, … the sql collation was set to binary to avoid errors with navision. the database gets automatically the server collation name, so the database has binary collation name. now our customer has to install citrix to bring access to the database for some remote users. when we try to connect to the server navision returns an error: the codepage in the computer is not the same codepage 850 installed on the database. we are making the test WITHOUT using citrix but in citrix server to test if navision client can connect to the server because citrix will use this navision client. please any suggestion… regards.
You need to have the same default language on the server as You client. /Lars
You need to check/change the ‘nls’ property, ACP key value in Registry. The value in this key should match the code page selected at database level for SQL Server.
Which version? I seem to remember an error like this with earlier version of the Financials 2.6 client that caused codepage errors. Workarounds exists, but upgrading to 2.6e solved the problem.
I laid out the full rules for code pages once. Try to search for code page or collation and you’ll find it. (By the way, your database can have any compatible collation when running SQL Server 2000, so I assume you’re still using 7.0). Don’t change this registry key - change your system code page properly using the System Default Locale in Control Panel’s Regional Settings - or in XP the Language under Advanced in Regional Options.
Hi Robert,
quote:
Don’t change this registry key - change your system code page properly using the System Default Locale in Control Panel’s Regional Settings - or in XP the Language under Advanced in Regional Options
This doesn’t work with us. Only thru’ change in Registry…ControlSet0001,ControlSet0002…Code Page…ACP value only Are we missing something?
Mohammed. Are you changing the system default locale? Not the user’s locale. The system default locale determines the ANSI/OEM settings. I can successfully change it on any Win2000, NT4, or XP machine without regedit.
The user locale. But with only change from Regional Settings for a user, the problem isn’t solved so we have to resort to changing his registry settings.
As I said, it is not the User locale that controls it. Use the Default locale.
ok client and server both need to have the same codepage… woah! 
thanks to all.