I am aware that there are many threads about this problem, but please hear me out: We are running 3.10A SQL Server Option with a 2.60 codebase.(We are upgrading our code to 3.70 this quarter) We have a Customer No. that is a sequential code field, all numbers. The SQL field type is Varchar, but it is really a number. When we converted to SQL, and it defaulted to varchar, we left it that way because it was too much work to change the field type. We have two companies that use the same convention for numbering. I am attempting a NAvision backup up of the db, for restore to 3.70, and to send to our NSC to begin coding upgrade. We have been using SQL backups all along. In one company, I get an Error 1190 in Module 19 message for the Customer No. field, in the other company I don’t get the error. I have looked at the threads surrounding this problem and I can state that: 1. Understanding how important it is to write records into Navision using Navision we have absolutely no applications that insert or update into this table through the SQL back-end 2. Since this field is a number, there is no uppercase / lowercase issues. So - my only solution to dataport the data out, delete and re-import? If out-delete-reimport fixes mixed case issues, then how will this help me with what is essentially an integer key? We have added many custom fields to Customer and I do not want to write a dataport where i have to export 100 fields (picking them one at a time) BTW: Is there a way to have the dataport use all fields without picking every one of them???), only to have it not fix my problem. I have looked at the data in SQL and I find no records with blank or odd characters in the No. field Please help
We have the same error in some of our databases. So far we have not exactly found out how to solve it, but one of our external consultants are working on it, so we hope… Our situation has been similar. But then again not. We upgraded from 2.60 to a 3.01 SQL database. My own guess to what was wrong is that while upgrading the collation was changed. The database is using Simplyfied Chinese, where no lower/uppercase exists. The error only occurs in CODE fields and just looking at it show us that’s wrong. When our consultant is done working on it, I will be happy to report more…
Here’s a suggestion. Try to use Data Transormation Services SQL tool and export only the Customer No. field to a text file. Zip it and send it to me at deanmccrae@hotmail.com. I would like to take a look at it.
I copied my db to a test location, deleted all the customers and ran a backup. I found two other tables (both our own custom tables) that needed to be dumped and reloaded in order for the backup to complete, but it did complete. Robert, I would be happy to zip up the customer numbers for you. Thanks for all of your help