January 4, 2007 at 4:29 pm
I'm migrating an application from Db2 and I have columns that have latin1 charactes in their names. When I try to import the data into SQL server I get the error below.
When I try to work from QA, I could do all of these things like:
CREATE TABLE [BÃÄÖÜéèê] (
[ID] [bigint] NOT NULL ,
[ABÃÄÖÜéèê] [varchar] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
) ON [PRIMARY]
GO
insert into BÃÄÖÜéèê values(1, 'test')
select ID, ABÃÄÖÜéèê from BÃÄÖÜéèê
where ABÃÄÖÜéèê=2
But if I ran the application then I have troubles.It might be a binding issue in the app?
Are the latin1 characters allowed in SQL server 2000/2005 and are there any limitations when this is a call through ODBC connections? Where can I look for help on that problem?
Thanks a lot, mj
[Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near '…'. ** AND ** [Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared.
01/04 10:29:17 [sql:3404] CRIT: Statement: Statement: sql=INSERT INTO ADDRESS(ADDR_ID,ABÃ…,ADDR1)VALUES(?,?,?,)
01/04 10:29:17 [sql:3404] CRIT: Bind Values: 3075001,'TEST','29 Alte Lubecker Chaussee'
01/04 10:29:17 [sql:3404] CRIT: CRITICAL ERROR[SQL-00001]: SQL call failed.
42000
January 8, 2007 at 8:00 am
This was removed by the editor as SPAM
January 9, 2007 at 2:16 am
You could try changing the datatype to nvarchar and the insert statement to
insert into [testtable] values (1, N'test')
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply