|
 |
access thread: Strange Error Message - Access/SQL Server/ADO
Message #1 by "Guy Harwood" <guy@h...> on Mon, 28 Jan 2002 09:40:39
|
|
Using Access XP to develop a Client/Server app with SQL server backend, i
get the following error when opening any table in my
database from the access project:
"ADO error: Cannot resolve collation conflict for column 2 in SELECT
statement"
The default Northwind and Pubs databases work fine if connected to my
project. does anyone have an idea as to what is wrong with mine??????
any help would be greatly appreciated.
Thanks in advance
Guy
Message #2 by brian.skelton@b... on Mon, 28 Jan 2002 10:38:35
|
|
Guy
Haven't got an answer, but maybe a pointer in the right direction.
I came across a similar error when trying to UNION two SQL Server tables
together. Apparently the two tables had been created with
different 'Collation' settings - somthing similar to Access's compare
order but much more complicated. There seems to be a collation setting for
each character set (1000's!) that SQL Server can work with.
I managed to get round my problem by explicitly setting the collate order
in my query with the COLLATE statement - this may not help you as you're
trying to open a table!
Talk to your SQL Server DBA if you can. Or try posting this question on
one of the SQL Server lists.
Brian
> Using Access XP to develop a Client/Server app with SQL server backend,
i
> get the following error when opening any table in my
> database from the access project:
>
> "ADO error: Cannot resolve collation conflict for column 2 in SELECT
> statement"
>
> The default Northwind and Pubs databases work fine if connected to my
> project. does anyone have an idea as to what is wrong with mine??????
>
> any help would be greatly appreciated.
>
> Thanks in advance
>
> Guy
|
|
 |