MS Access and MyODBC 5

[Eugene-61]

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.

[Imran Abizar]

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/myodbc?unsub=lists@...

[Eugene-61]

Imran,
I've mentioned that trying to use User / System DSN results in Access 2003
crash while opening linked table. Anyway, thank you - I'll try to create DSN
file by hand.

----- Original Message -----
From: "Imran Abizar" <imranh@...>
To: "Eugene" <jevobz@...>
Cc: <myodbc@...>
Sent: Thursday, June 12, 2008 9:51 PM
Subject: 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/myodbc?unsub=lists@...

[Jerry Schwartz-2]

>-----Original Message-----
>From: Eugene [mailto:jevobz@...]
>Sent: Thursday, June 12, 2008 2:58 PM
>To: myodbc@...
>Subject: Re: MS Access and MyODBC 5
>
>Imran,
>I've mentioned that trying to use User / System DSN results in Access
>2003
>crash while opening linked table. Anyway, thank you - I'll try to create
>DSN
>file by hand.
>

[JS] This isn't very helpful, but I've used both MyODBC 3.x and MyODBC 5.x
with both MS Access 2003 and MS Access 2007. I've used both System and User
DSNs. I have run into what I believe is a bug in MS Access 2007: I can't run
a query against MySQL unless I open a table first.





--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/myodbc?unsub=lists@...

[Eugene-61]

Could not agree with you more, Vladimir!
I've also noticed that after MyODBC 3.51.07 there's no working ODBC driver at all - that's the cost of declared "cross-platform compatibility"
And GA status assigned to 5.1 driver is nothing but a joke...not the best one
  My opinion is that it is not clever to use MyODBC 5.1 yet. It is still not production ready. Problems you mentioned are just few of them.

  best regards

  Vladimir Drobnjak
  tel. [phone]
  mobil. [phone]

[Imran Abizar]

Hi,

I am not sure if you have an option of using another tool as an
alternative to MS Access. If you do, I recommend using WinSQL
(synametrics.com). It works pretty well with the new driver.

Another suggestion is to enable ODBC tracing and find out which call is
causing the problem and then submit a bug report with MySQL.

Imran.



Eugene wrote:

> Could not agree with you more, Vladimir!
> I've also noticed that after MyODBC 3.51.07 there's no working ODBC driver at all - that's the cost of declared "cross-platform compatibility"
> And GA status assigned to 5.1 driver is nothing but a joke...not the best one
>   My opinion is that it is not clever to use MyODBC 5.1 yet. It is still not production ready. Problems you mentioned are just few of them.
>
>   best regards
>
>   Vladimir Drobnjak
>   tel. [phone]
>   mobil. [phone]
>  

--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/myodbc?unsub=lists@...