Unicode Conversion Failed error message

[programmher]

I am inserting data into a SQL 7 database. One of my fields is an autonumber field. The datatype of this field is "int" and I have selected the Identity seed option. I get the below message whenever I attempt to update my data into the table:

[MERANT][ODBC SQL Server Driver]Unicode conversion failed

What am I missing? I have searched Microsoft's knowledge base and their entire site. I have not been able to locate any clear explanation.

Please advise. Any assistance is GREATLY appreciated...

 

[TomSark]

Are you trying to insert a character-based value in the field? Unicode only applies to character-based fields...

Tom

 

[programmher]

Tom,

This is an autonumber field. Numbers (in this case, 1) are being (or attempting to be) inserted into this field.

 

[TomSark]

Yes, but is it a character '1' that you are trying to insert into the table? BTW... autonumber = identity in SQL Server...

Tom

 

[programmher]

Tom,

The "identity" option is on within my SQL table. The character "1" is also automatically created by the incremental identity seed.

I now am attempting to retrieve records from my table using a simple Select * From tbl_MyTable and am getting the same message! I am not performing any updates - just requesting all the records.

Have you seen this before and do you have a solution? I would appreciate any insight.

 

[TomSark]

I see... now I have some questions...

Has there been a change to the sort order, character set, or the unicode collation settings on the server?

How did the data in the table originally get populated?

Are you running the query on your machine that has SQL Server installed on it where the data resides on another server?

Has this worked before or did this just start happening?

Has there been a recent restore of any databases on your
server? The master database?

I'll also be checking around technical sources for this...


Tom

 

[TomSark]

I found this on technet:

Unicode conversion failed. The code page of the SQL server must be installed on the client system.

The server code page must exist on the client for proper operation. Either clear the Auto Translate check box for the DSN or install the code page of the server on the client. The server code page can be determined by running EXEC sp_server_info 18.


Hope this helps....

Tom

 

[programmher]

Tom-

No, there has not been a change t the sort order, character set, or unicode collation setting on the server.

This is a new table I just created. It is not yet populated with data.

I am currently running the query on your machine that has SQL Server installed on it. The the data is residing on another server?

This just started happening. I have not created a table with identity/autonumber features and attempted to update the table from a CF form.

No to both of these questions. Has there been a recent restore of any databases on your
server? The master database?

As for your last comment; I located that tip and tried it. It did not work.

Thanks for attempting to assist me. PLEASE let me know if you locate any other information!

Thanks again!

 

[TomSark]

What are your settings in your client newtork utility, db library options tab?

Tom

 

[programmher]

Tom,

I found some info on Allaire's website/white pages. It references unicode conversion failures when operatinf CF on an Apache Server and Linux OS. This might be my problem; however, it doesn't address why my simple select statement returns the error and more complex queries do not.

I will check the setting and db library options.