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. Code:
ODBC -- call failed. (Error 3146) Excel apparently relies on something called Microsoft Query to do the dirty work for it. It gives: Code:
User cancelled. Code:
Driver error. Code:
Couldn't read this file. Code:
Couldn't read this file. 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.) |
Hello,
is the ODBC-Data source configured as System-Datasource? (The Systemdatasource tab when configuring the datasource) |
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) |
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 |
????
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. |