Re: MS Access and MyODBC 5

Eugene,

First, a question: Do you have to use a File DSN? Why not a User or 
System DSN?

Here is a work-around of what you can do. File DSNs are nothing by a 
plain text file in INI format containing the connection string (without 
semicolons). Therefore, you can manually modify the .dsn file and put 
the connection parameters in there. I am pasting the contents of a 
sample file I created on my machine that works with 5.1 driver. FYI: You 
can use WinSQL (synametrics.com) to create connection strings.

Sample File DSN.


[ODBC]
DRIVER={MySQL ODBC 5.1 Driver}
DATABASE=YourDBName
OPTION=0
PWD=password
PORT=0
SERVER=YourServerHostName
UID=loginID


Best regards,
Imran.




Eugene wrote:
> Greetings everyone,
>
> I use Access with MySQL for 5 years. This combination is quite reliable, but last well-working ODBC driver for me is 3.51.07
> I cannot get MyODBC 5.1 working with Access 2003 at all, despite its "Generally Available" status:
>
> It is not possible to create File DSN through ODBC manager (ODBC manager returns "General error" message)
> AND
> although it is possible to create System or User DSN and link table to Access 2003, when I try to open it (simply open, from Tables list) Access crashes
>
> So, in my situation (Access + MySQL) MyODBC 5.1.4 is completely useless
>
> Now some technical details:
> Both server (5.0.51a) and client (MyODBC 5.1.4) run in Windows XP on the same machine (same things happen with remote MySQL on Win 2003 Server)
> Custom cp1257 collation XML file (used since MySQL 4.0 to correctly sort Lithuanian strings)
> MS Access 2003 SP2
>
> My question is, what should I do - fill new Bug in bugs.mysql.com or problems like I've just described are already known.
>   

-- 
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/[email protected]