Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 295 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Unicode with SQL Server (Reporting)
Benno67
Member Posts: 39
Hi All,
We are trying to tackle the old Unocode problem in Dynamics NAV. We think we found all topics on subject, both on Mibuso and the Internet. We also tried the regional code page solution, and looked at the Octocon trick, but it still isn’t good enough.
Our customer is selling goods from the Netherland to Poland and Russia. We solved the problem of printing documents with a Polish and a Russian client, but the problem that reviewing the documents with a Dutch client will produce faulty output.
On the Mibuso conference I asked Michael Nielsen if he could give a solution (I asked when Dynamics NAV would be available for Unicode), and he did come up with a brilliant suggestion : SQL Server is storing all data in Unicode format, producing the required documents with SQL Reporting should produce documents in Polish or Russian not depending on the Dynamics NAV client language.
With the WEB Service SQL Reporting trick SQL Reporting can be used for Dynamics NAV 4/5, so it will be a solution also for older installation.
So we tried.. The only problem is that SQL Server (2005) will store Unicode only in Nchar- and Nvarchar fields. Data stored in Char field will be converted to the default language setting of the SQL instance. No problem to change the SQL varchar fields to nvarchar, but after doing so Dynamics NAV does not recognize the nvarchar as a valid “text” field.
So we are stuck again. Any suggestions?
Benno
We are trying to tackle the old Unocode problem in Dynamics NAV. We think we found all topics on subject, both on Mibuso and the Internet. We also tried the regional code page solution, and looked at the Octocon trick, but it still isn’t good enough.
Our customer is selling goods from the Netherland to Poland and Russia. We solved the problem of printing documents with a Polish and a Russian client, but the problem that reviewing the documents with a Dutch client will produce faulty output.
On the Mibuso conference I asked Michael Nielsen if he could give a solution (I asked when Dynamics NAV would be available for Unicode), and he did come up with a brilliant suggestion : SQL Server is storing all data in Unicode format, producing the required documents with SQL Reporting should produce documents in Polish or Russian not depending on the Dynamics NAV client language.
With the WEB Service SQL Reporting trick SQL Reporting can be used for Dynamics NAV 4/5, so it will be a solution also for older installation.
So we tried.. The only problem is that SQL Server (2005) will store Unicode only in Nchar- and Nvarchar fields. Data stored in Char field will be converted to the default language setting of the SQL instance. No problem to change the SQL varchar fields to nvarchar, but after doing so Dynamics NAV does not recognize the nvarchar as a valid “text” field.
So we are stuck again. Any suggestions?
Benno
0