|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
MS Access and MyODBC 5
Greetings everyone,
I use Access with MySQL for 5 years. This combination is quite reliable, but last well-working DBC driver for me is 3.51.07 I cannot get MDBC 5.1 working with Access 2003 at all, despite its "Generally Available" status: It is not possible to create File DSN through DBC manager (DBC 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) MDBC 5.1.4 is completely useless Now some technical details: Both server (5.0.51a) and client (MDBC 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. |
|
#2
|
|||
|
|||
|
MS Access and MyODBC 5
Could not agree with you more, Vladimir!
I've also noticed that after MDBC 3.51.07 there's no working DBC driver at all - that's the cost of declared "cross-platform compatibility" And GA status assigned to 5.1 driver is nothing but a jokenot the best one My opinion is that it is not clever to use MDBC 5.1 yet. It is still not production ready. Problems you mentioned are just few of them. best regards Vladimir Drobnjak tel. +386-5-6271824 mobil. +386-51-418158 |
![]() |
| Viewing: Web Development Archives > Mailing Lists > MYSQL > MS Access and MyODBC 5 |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|