[prev in list] [next in list] [prev in thread] [next in thread]
List: mysql-odbc
Subject: RE: the driver never appears in the Administrator
From: Paul Wilson <wilson106 () llnl ! gov>
Date: 2006-02-09 22:09:35
Message-ID: 6.2.1.2.2.20060209135809.02450898 () mail ! llnl ! gov
[Download RAW message or body]
Hi, Lawson:
That worked perfectly. The driver appeared in the Administrator, and I was
able to create and test ODBC datasources. Thank you!
I will be very interested to try interface packages for MySQL other than
ODBC. For instance, I have already made sure that I can do everything my
applications need to do in the database using Java and JDBC.
Wherever I have worked, the big preferences have been to connect to
databases using ODBC and JDBC. Therefore, I need to check out MyODBC and
find out whether it enables me to do at least the minimum that my
applications have to do.
Thank you again, Lawson. I was just about ready to throw in the towel.
Paul
At 11:40 AM 2/9/2006, Lawson Cronlund wrote:
>Paul,
>
>I found it. It was actually where it should be - in the MysQLODBC directory
>of my MySQL archive/download files.
>
>Here's the text of my note on this which I got from the MySQL ODBC list (I'm
>pretty sure that was the source). This worked for me. I think I did a
>restart after following the instructions - just in case.
>
>============ ODBCDriverAbsenceCorrection.txt =======================
>If, after you install MyODBC, you cannot find the MySQL ODBC driver listed
>in the Windows
>ODBC Manager, the following registry change may be needed.
>
>As always, when changing the registry, make a backup copy prior to any
>changes and
>be prepared to restore the registry from the backup.
>
>1. Select the registry key:
> HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers
>2. Delete the (Default) key.
> Note that the key does not actually delete. The value changes to
>"(value not set)".
>3. Restart the computer.
>4. Display the installed drivers in the ODBC manager.
> You should see the MySQL driver installed now.
>======================================================================
>
>You might want to investigate the direct interface packages such as
>VBMySQLDirect (for MS Visual Basic) or the other language packages for other
>languages. I found this to be a better solution for my application since I
>had trouble with the ODBC package. There are rumors that a much, much
>better than new ODBC package is going to arrive in the near (or far?) future
>but I haven't seen anything that identifies when yet.
>
>Regards.
>
>
>
>Lawson
>lawson@vrtinc.com
>+1(480)308-0641 (Voice)
>+1(602)996-0376 (Fax)
>
--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=mysql-odbc@progressive-comp.com
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic