Import FBK backup into a new SQL2005 database fails

pavel.kotrba

Hi there,
I'm trying to import a FBK backup into a new SQL2005 database and receive the following error:

The table post code contains data that can't be used with Microsoft Business Solutions-Navision.
Field: search city
Data: VUFFLENS-CHœTEAU

---
source: Navision 4.0sp2 Version3 / SQLserver 2005 english (9.0.2047) sp1 / server collation = SQL_Latin1_General_CP1_CI_AS / database collation = Latin1_General_CI_AS / OS Windows 2003 (german)
---
destination: another Server, same software: Navision 4.0sp2 Version3 / SQLserver 2005 english (9.0.2047) sp1 / server collation = Latin1_General_CI_AS / database collation = Latin1_General_CI_AS / OS Windows 2003 (german)
---

The source database contains swiss data and thus the table post code contains also german, italian and french letters and notation. The data of the affected field is the name of a town: VUFFLENS-CHTEAU and the letter '' causes the problem - it turns into 'œ'.

I also tried to import the demo database.fbk from the (swiss) setup CD which contains the same data in the post code table, but this worked fine, no error.

Has anybody an idea or a workaround for this issue?
I noticed the difference in the Sql server collation (despite both sql server were installed with default values). But this can't cause the problem as the demo fbk works fine... or am I wrong?

Thanks for any suggestions!
Pavel

kriki

A week ago, I had the same problem.
I restored the DB in a Navision DB, searched for the record that gave problems, deleted or modified it so the characters are accepted by SQL2005.
Backed up from the Navision DB and restored in SQL2005.

PS : to speed up the restore in the Navision-DB:Once Navision starts rebuilding the secondary indexes, stop it, delete the secondary indexes from the tables (only the ones with a lot of records) and let it continue the restore. The rebuilding the secondary indexes will be a lot faster.

jwikman

I've got the same error while restoring a backup from a Native DB to SQL2005.

It seems like Navision SQL Client checks code-fields and does not allow lower-case letters, like 'œ'.

If you restore a database from a windows client with other regional settings than the clients that you run Navision this can happen because of some unicode convertions. Check that your Windows client has the correct settings in Control Panel->Regional and Language options->Advanced tab->Language for non-Unicode programs.

It worked for me.

pavel.kotrba

Thank you for the suggestions!
Meanwhile I created a new native database, restored the backup, changed the affected record in the post code table (VUFFLENS-CHTEAU into VUFFLENS-CHATEAU) and created a new backup FBK.

Then I imported the new FBK file into a new SQL database - without any error - and also changed the affected data back to VUFFLENS-CHTEAU. This worked at last - with a disproportionate effort - but in the case of emergency it would be an dreadful exercise...

btw. I also checked the regional settings but they're the same on source and destination computer.

Thanks again!
Pavel