473,289 Members | 2,089 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,289 software developers and data experts.

ODBC Version trouble between 3.51.10.00 and 3.51.11.00

Dear group,

we are dealing with some very specific problems with ODBC, where a
connection from SQL-Server to Mysql works with ODBC-driver 3.51.10.00
and does NOT work with ODBC-driver 3.51.11.00. Maybe someone
experiences similar problems or even has a solution ? Some feedback (to
the group) would be highly appreciated.

We use a Microsoft SQL-Server as Headquarter database and some
Mysql-machines on Redhat as satellite-databases. We use a script to
copy and replicate data between satellite and headquarter. This script
is using simple SQL connecting to Mysql-database using ODBC and
"Openrowset".

In order to copy only new data from sattelites we use the
Binary_Checksum function from Microsoft SQL-Server. This works with the
3.51.10.00 version perfectly but it fails with the 3.51.11.00 version,
where it gives us the message (from MS-SQL-Server) "msg 8481 Error
expanding "*": all columns incomparable, '*' expanded to zero columns".
This message comes only for some but not for all statements using the
binary_checksum.

The only way to fix this is to stick with the "old" version of the
ODBC-driver. Could someone please explain what is going one?

I will post this also in the relevant newsgroup of MS-SQL-Server

Thanks

greetings from Vienna

Uli

Jul 23 '05 #1
2 2222
ul*********@lycos.at wrote:
Dear group,

we are dealing with some very specific problems with ODBC, where a
connection from SQL-Server to Mysql works with ODBC-driver 3.51.10.00
and does NOT work with ODBC-driver 3.51.11.00. Maybe someone
experiences similar problems or even has a solution ? Some feedback (to
the group) would be highly appreciated.

We use a Microsoft SQL-Server as Headquarter database and some
Mysql-machines on Redhat as satellite-databases. We use a script to
copy and replicate data between satellite and headquarter. This script
is using simple SQL connecting to Mysql-database using ODBC and
"Openrowset".

In order to copy only new data from sattelites we use the
Binary_Checksum function from Microsoft SQL-Server. This works with the
3.51.10.00 version perfectly but it fails with the 3.51.11.00 version,
where it gives us the message (from MS-SQL-Server) "msg 8481 Error
expanding "*": all columns incomparable, '*' expanded to zero columns".
This message comes only for some but not for all statements using the
binary_checksum.

The only way to fix this is to stick with the "old" version of the
ODBC-driver. Could someone please explain what is going one?

I will post this also in the relevant newsgroup of MS-SQL-Server

Thanks

greetings from Vienna

Uli


It seems to me that the asterisk (*) sign is not evaluated properly in
the link using the lastest ODBC driver. Is it true that the error only
happens for statements like below?

SELECT * FROM ...

or

SELECT COUNT(*) ...

Or do these errors also occur in queries which do not contain a asterisk?

This is only a guess as I am not familiar with communication between
mySQL and Microsoft SQL servers.

Is there an explicit reason for upgrading your ODBC driver? If not I
would leave it like it is as the upgrade is a minor version change I guess.

Something else (you might already have considered): Is it not possible
to port the main 'Headquarter' database to mySQL as well? You can in
that situation make use of replication to sync your databases at all
servers. Especially when you use ODBC for the application to communicate
with the application this should be relatively simple, as you probably
don't have to change much in your application.

Jonathan

--
A: Because it messes up the order in which people normally read text.
Q: Why is it such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
Jul 23 '05 #2


Jonathan schrieb:
ul*********@lycos.at wrote:
Dear group,

we are dealing with some very specific problems with ODBC, where a
connection from SQL-Server to Mysql works with ODBC-driver 3.51.10.00
and does NOT work with ODBC-driver 3.51.11.00. Maybe someone
experiences similar problems or even has a solution ? Some feedback (to
the group) would be highly appreciated.

We use a Microsoft SQL-Server as Headquarter database and some
Mysql-machines on Redhat as satellite-databases. We use a script to
copy and replicate data between satellite and headquarter. This script
is using simple SQL connecting to Mysql-database using ODBC and
"Openrowset".

In order to copy only new data from sattelites we use the
Binary_Checksum function from Microsoft SQL-Server. This works with the
3.51.10.00 version perfectly but it fails with the 3.51.11.00 version,
where it gives us the message (from MS-SQL-Server) "msg 8481 Error
expanding "*": all columns incomparable, '*' expanded to zero columns".
This message comes only for some but not for all statements using the
binary_checksum.

The only way to fix this is to stick with the "old" version of the
ODBC-driver. Could someone please explain what is going one?

I will post this also in the relevant newsgroup of MS-SQL-Server

Thanks

greetings from Vienna

Uli


It seems to me that the asterisk (*) sign is not evaluated properly in
the link using the lastest ODBC driver. Is it true that the error only
happens for statements like below?

SELECT * FROM ...

or

SELECT COUNT(*) ...

Or do these errors also occur in queries which do not contain a asterisk?

This is only a guess as I am not familiar with communication between
mySQL and Microsoft SQL servers.

Is there an explicit reason for upgrading your ODBC driver? If not I
would leave it like it is as the upgrade is a minor version change I guess.

Something else (you might already have considered): Is it not possible
to port the main 'Headquarter' database to mySQL as well? You can in
that situation make use of replication to sync your databases at all
servers. Especially when you use ODBC for the application to communicate
with the application this should be relatively simple, as you probably
don't have to change much in your application.

Jonathan


Dear Jonathan, thanks for the response,

1) It is not possible to switch the whole architecture to MySQL.
(political reasons blah)
2) It happens only with some SELECT a.*,1 from OPENROWSET(...., select
* from ...) a not for all and i think it has to do something with
characters and collation
3) we can live with the lower version of ODBC since it works, but we
would like to see that it this error will be removed from further
versions of the ODBC-driver
4) Did you ever try to remove a higher version ODBC-driver from a
Windows registry / system in order to install a lower version. It is
virtually impossible. We re-installed the whole system, just to make
sure...

Regards

Uli

Jul 23 '05 #3

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
by: Spiggy Topes | last post by:
Hi I have a Visual Basic application that uses ADO to access an Oracle database. I have the latest 9.x ODBC drivers installed, and SQL*Plus tells me I'm looking at Oracle 8i release 8.1.7.4.1...
2
by: J. Marshall Latham | last post by:
I have a simple page trying to enter three pieces of information into a database using ODBC on a web site that has .NET Framework 1.0, so I have to use this Microsoft.Data.Odbc.dll which has been...
5
by: Alec | last post by:
Hi All, I am currently trying to link in Access 97 to a table in a MSSQL 7 server. Initially the link is fine, however, when I close the access database and re-open it from the same network...
4
by: Eric E | last post by:
Hi all, I'm having quite a bit of trouble with code to create linked tables in Access 2K. I create a DAO tabledef using CreateTableDef against a DAO database object, then set its connection...
7
by: Richard Marsden | last post by:
(also posted to microsoft.public.access.odbcclientsvr but no reply so far: problem concerns ODBC->MS Access) I have some ODBC code that I'm testing against various underlying databases. The...
2
by: xiaotom | last post by:
I want my software to be independant of operation system and databases. That's why I want to use odbc, and don't want to use MFC. Here I have some questions to ask: 1. On unix (like sun...
4
by: StefanSerena | last post by:
Hi I'm running Windows 2000 and Office 2003. I want to copy tables from an unknown database format into Access 2.0 and I could do it quite easily if it weren't for the fact that recent...
3
by: zombiechewtoy | last post by:
I'm having trouble making an ODBC connection using VB.NET 2005. I have tried nearly every connection string found on connectionstrings.com, in almost every format I can think of. I have tried...
0
by: elias.farah | last post by:
Hi Everyone, I'm having a lot of trouble with Access 2007 / Vista x64 creating a new ODBC table. Existing ODBC tables are fine, and connect - however creating a new ODBC tables via the visard...
2
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 7 Feb 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:30 (7.30PM). In this month's session, the creator of the excellent VBE...
0
by: DolphinDB | last post by:
The formulas of 101 quantitative trading alphas used by WorldQuant were presented in the paper 101 Formulaic Alphas. However, some formulas are complex, leading to challenges in calculation. Take...
0
by: Aftab Ahmad | last post by:
So, I have written a code for a cmd called "Send WhatsApp Message" to open and send WhatsApp messaage. The code is given below. Dim IE As Object Set IE =...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: marcoviolo | last post by:
Dear all, I would like to implement on my worksheet an vlookup dynamic , that consider a change of pivot excel via win32com, from an external excel (without open it) and save the new file into a...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: Vimpel783 | last post by:
Hello! Guys, I found this code on the Internet, but I need to modify it a little. It works well, the problem is this: Data is sent from only one cell, in this case B5, but it is necessary that data...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.