LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   MySQL ODBC Driver problem (with MS Windows) (https://www.linuxquestions.org/questions/linux-software-2/mysql-odbc-driver-problem-with-ms-windows-382357/)

gd2shoe 11-12-2005 03:19 AM

MySQL ODBC Driver problem (with MS Windows)
 
This is a Windows / Linux integration problem.

I am getting ready to set up a MySQL database that will require data to be collected and then displayed in pretty graphs and such. At this point, I think my best bet will be to have Microsoft Excel connecting to my database through the ODBC driver. Now I can get this to work beutifully on my test systems, if the password is typed into the ODBC connection configuration. I cannot get it to work when asking for a password upon making a connection attempt.

I'm using the "MySQL Connector/ODBC 3.51" driver for windows to connect to a "MySQL 4.0.10a" server accross a local area network (they are plugged into the same hub). I'm using Windows XP home at the moment.The Linux firewall is opened on the port in question. I used the provided md5sum to confirm that the driver was properly downloaded from www.mysql.com. The query browser and Administrator programs are both installed and work admirably. I have reinstalled the driver several times.

From Access, I get this error (typed in, not selectable):
Code:

ODBC--call failed.
[MySQL][ODBC 3.51 Driver]User cancelled. (#0)

The help button gives this:
Code:

ODBC -- call failed. (Error 3146)
Using an ODBC connection, you tried to perform an operation on data in an ODBC data source. This error may occur when the ODBC data source is on a network drive and you are not connected to the network. Make sure the network is available, and then try the operation again.


Excel apparently relies on something called Microsoft Query to do the dirty work for it. It gives:
Code:

User cancelled.
It's help button:
Code:

Driver error.
This error was returned by the driver. For more information, check the documentation for the driver you are currently using.

Followed by (probably a generic error):
Code:

Couldn't read this file.
And yet another help button:
Code:

Couldn't read this file.
Microsoft Query can't read your file. The file may not be in Microsoft Query or Q+E format, there may be a disk error, or the file may be corrupted.

Note that these errors occur when and only when the password is not specified in the connection configuration. In each case, it pops open a window that lets me specify connection details, including a password field.

I've tried googleing for the answer, but cannot find anything sufficiently close to the problem that I'm having.

What else should I try? I know that I can restrict access in the database to a specific account, on a specific IP address, but that computer will be accessible by too many people. I want to be able to require a password be typed by the end user.

(And any good suggestions on SQL or MySQL for noobs would be appreciated.)

karpi 11-14-2005 04:46 AM

Hello,

is the ODBC-Data source configured as System-Datasource?
(The Systemdatasource tab when configuring the datasource)

gd2shoe 11-14-2005 09:38 AM

No. I'm fairly new to databasing. How would that matter?

I have thought about adding a new user account, and password protecting that, but that would be a hassle to use and I am trying to eliminate hassle. (besides being a very visible kludge)

karpi 11-14-2005 10:34 AM

Hello,

a System-Datasource is available to all users on your XP-box.

When setting up the ODBC-Datasource you can test the Connection. This gives detailed error-messages.

HTH

gd2shoe 11-14-2005 01:50 PM

????

As I said "How would that matter?"

I already know that the connection works as perfectly as I can tell. I can test it to my hearts content if, and only if, I input the password directly into the connection setup.

If the password is put into the connection setup, it does not ask for a password when the data source is used. It connects beautifully.

If a password is not provided in the connection setup, it asks for a password, and does not connect even if the password you give it is correct.

I do not see how making the connection a "System-Datasource" is going to change anything other than the user accounts that can access it. I do not need multiple accounts accessing the data source. I just need it to ask for a password.

How would you propose that I can use a system wide data source to diagnose this particular problem?


All times are GMT -5. The time now is 07:33 AM.