Bug #22298 The driver is incapable of supporting the current environment attributes. (#0)
Submitted: 13 Sep 2006 7:31 Modified: 30 Oct 2007 13:32
Reporter: Oszkár Horváth Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / ODBC Severity:S3 (Non-critical)
Version:5.1 OS:Any
Assigned to: CPU Architecture:Any
Tags: access, access 2003, access 97, connect, environment attributes, fail, MyODBC

[13 Sep 2006 7:31] Oszkár Horváth
Description:
Hi!

I used MySQL+Access to view my tables. MySQL 5.0 and MyODBC 5.0.4 are on my new laptop and I can't get it to work anymore, I have tried both Access 97 and Access 2003. Creating ODBC works OK, but when I try to link a table to Access, I receive the following error:

[Microsoft][ODBC Driver Manager] The driver is incapable of supporting the current environment attributes. (#0)

The same versions worked with my previous Windows on my previous laptop. As for the attributes, I don't know what (and where) to change, all I have done MySQL 5.0 related is UPDATE user SET password=OLD_PASSWORD('****') WHERE user='root'; FLUSH PRIVILEGES; to maintain compatibility.

Thank you!

How to repeat:
- setup MySQL 5.0 (mysql-5.0.24a-win32-setup.exe)
- setup mysql-connector-odbc-noinstall-5.0.4-alpha-win32
- set database privileges and use OLD_PASSWORD function
- create an ODBC link to a database
- try to link table to Access97 or Access2003 - even before showing the tables, ODBC will fail showing the above error message

OS: Windows XP SP2 up to date (new installation).
[13 Sep 2006 9:43] Tonci Grgin
Hi Oszkár and thanks for your problem report.
Quote from Readme.txt for c/ODBC 5:
The driver will not work with ADO or complex applications such as Microsoft Office at this time, but should do so by Milestone 5.
Notice that if a bug is caused by missing functionality, we will defer processing it until that functionality has been implemented. However, if you find bugs with the functionality listed above, then we’ll be working to address those issues in the next milestone release (if possible).

What puzzles me is that you claim c/ODBC 5 working on your previous install. Is this correct? Could it be that it was MyODBC 3.51.xx after all?
[13 Sep 2006 10:30] Oszkár Horváth
Dear Tonci! Thank you for your comment. Probably I was using 3.51, because that works fine with both Access97 and Access2003. Access2003 even handles the UTF-8 characters without having to convert with scripts manually. 

I have the ODBC 5.0.4 install set, that's why I must have thought I was using it, but now I'm sure I wasn't. Thanks for your competent and fast help!

Oszkár
[13 Sep 2006 13:53] Tonci Grgin
Oszkár, no problem. Thank you for your interest in MySQL.
[17 Oct 2007 13:52] Susanne Ebrecht
This bug is a duplicate of bug #16178.
[30 Oct 2007 10:41] Susanne Ebrecht
I'll re-open this, because this could happen not only because of the character '*'  at the password.
[30 Oct 2007 13:32] Susanne Ebrecht
Hi,

many thanks for trusting MySQL.
Please try our new MyODBC version 5.1.

Your problem shouldn't occur there. I'll close this bug now. If you unexpected have already this problems, feel free to open it again.

Kind Regards,

Susanne