MySQL Connector/ODBC 5.0.5 has been released

Hello ODBC Users,

Connector/ODBC v5.0.5 (the first BETA release) has been released. You no
longer need to have Connector/ODBC 3.51 installed (however this release
can co-exist with a 3.51 installation), as this version now uses its own
setup library unlike prior ALPHA releases.

It is availble for download at
http://dev.mysql.com/downloads/connector/odbc/5.0.html

Connector/ODBC 5.0 is meant to be used with MySQL-5.0 and newer, as it
relies on information available in INFORMATION_SCHEMA when fulfilling
requests for metadata.

License
-------

MySQL Connector/ODBC is licensed under the GPL or a commercial license
from MySQL AB.

If you have licensed this product under the GPL, please see the COPYING
file for more information.

There are special exceptions to the terms and conditions of the GPL
as it is applied to this software. View the full text of the
exception in file LICENSE.exceptions in the directory of this
software distribution.

If you have licensed this product under a commercial license from
MySQL AB, please see the file "MySQLEULA.txt" that comes with this
distribution for the terms of the license.

Installation
------------

1) Unzip the archive containing Connector/ODBC 5.0 (if you're reading
this file from the archive, then you've already done this).

2) From a shell and in the base subdirectory of the Connector/ODBC 5.0
directory created when you unzipped the archive, do the following:

C:...> install 0

(if you're upgrading from the previous Connector/ODBC 5.0 release,
instead run "Upgrade.bat")

This should register the driver and copy the driver to
%SystemRoot%\System32

Current State of Implementation
-------------------------------
This driver is meant to be used with MySQL-5.0 and newer, as it relies
on information available in INFORMATION_SCHEMA when fulfilling requests
for metadata.

The driver is feature complete, and has started going through internal
testing. At this time it is known to be able to link tables in Microsoft
Access and perform some ADO-related functionality. Our goals for
internal testing are to cover the set of applications that are most used
with MySQL and ODBC, including Microsoft Office applications (including
Access), Crystal Reports, ADO and OleDB.

With this release we're asking the user community to give detailed
feedback on which applications do not work with the driver, as we don't
have access to all possible combinations of MDAC, Microsoft Office
service pack and hotfix combinations for our own internal testing. We're
also especially interested in results from testing in-house or
commercial applications that don't have widespread availability.


Reporting Bugs with this Release
--------------------------------
Please report bugs you find with this release at http://bugs.mysql.com/

For more expedient processing of your Connector/ODBC 5.0 bugs, please
make sure to record the version number with a “5.0” in it so that we
find them quicker when putting together fix lists.

Please include driver and driver-manager traces with your bug reports,
as this helps us isolate the bug much quicker. If your application works
with Connector/ODBC 3.51 but not 5.0, please enclose driver and driver
manager traces from 3.51 as well.

It is also very helpful if you include which version of MDAC and
associated DLLs you are using. Microsoft's MDAC version checker makes
this relatively straightforward. Instructions for installing and running
the MDAC version checker are at http://support.microsoft.com/kb/301202


Roadmap for Future Releases
---------------------------
Future beta releases will introduce new platforms (the code is written
in a cross-platform manner, we're just working out some small issues,
starting with Linux and then progressing to other Unix platforms).

We also include a graphical MSI-based installer in a future beta release
for the Microsoft Windows platform.

This beta does have some debug-related code, and is not entirely
optimized (it is sometimes "chattier" with the database server than 3.51
for example), as the first goal was to have something that is written
exactly-to-spec for the ODBC API specification, and "back off" where
testing shows that we can (or need to, in the case with some
applications). Future releases will be more performance-oriented than
the first few beta releases.

Regards,

-Mark
--
Mark Matthews
MySQL AB, Software Development Manager - Connectivity
www.mysql.com



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

Re: MySQL Connector/ODBC 5.0.5 has been released

On 10/17/06, Mark Matthews wrote:
> Connector/ODBC v5.0.5 (the first BETA release) has been released. You no
> longer need to have Connector/ODBC 3.51 installed (however this release
> can co-exist with a 3.51 installation), as this version now uses its own
> setup library unlike prior ALPHA releases.

> The driver is feature complete, and has started going through internal
> testing. At this time it is known to be able to link tables in Microsoft
> Access and perform some ADO-related functionality. Our goals for
> internal testing are to cover the set of applications that are most used
> with MySQL and ODBC, including Microsoft Office applications (including
> Access), Crystal Reports, ADO and OleDB.
>
> With this release we're asking the user community to give detailed
> feedback on which applications do not work with the driver, as we don't
> have access to all possible combinations of MDAC, Microsoft Office
> service pack and hotfix combinations for our own internal testing. We're
> also especially interested in results from testing in-house or
> commercial applications that don't have widespread availability.


Guys. First of all: congratulations with this new release, it is
another step forward. But... I'd like to know how much of a step. I
see 19 verified bugs in the ODBC section that name 5.0. Some of them
are obviously 3.51 related, but at least two are mine and thus 5.0.4.
One of those two still pertains in this new version (even if it was
reported back in July), given the new bug report 23375.
As I have said before: I am happy to go bug-hunting, but I see not
much feedback on this. I have not seen any progress report (neither in
the list, nor in the publication of the new version and not even in
the buglist) and this new version clearly still contains at least one
older bug. My other bug described the problem of not being able to
call stored procedures, which for me is rather important. Does 5.0.5
solve #20963? If not, then installing it (for me) is useless.

Once again: I admire your work and I know this is an open source
project. The only thing I am stressing is that the (at least my)
willingness to participate is heavily correlated with the amount of
feedback and sense of being heard.

Regards,

Frank

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

Re: MySQL Connector/ODBC 5.0.5 has been released

I tried at the last release and also this one, but has never got any
further than to trying to create an ODBC connection: Crash #¤#"%&!!

"odbcad32.exe has encountered a problem ans needs to close. We are sorry
for the inconvenience"
AppName: odbcad32.exe AppVer: 3.525.1117.0 ModName: Unknown, ModVer:
0.0.0.0 OffSet: 00c14220-
And then a one kilometer long error report where you can't copy/paste from.

Seems to me as if this product is not nearly ready for beta testing.


Frank Maas wrote:
> On 10/17/06, Mark Matthews wrote:
>> Connector/ODBC v5.0.5 (the first BETA release) has been released. You no
>> longer need to have Connector/ODBC 3.51 installed (however this release
>> can co-exist with a 3.51 installation), as this version now uses its own
>> setup library unlike prior ALPHA releases.
>
>> The driver is feature complete, and has started going through internal
>> testing. At this time it is known to be able to link tables in Microsoft
>> Access and perform some ADO-related functionality. Our goals for
>> internal testing are to cover the set of applications that are most used
>> with MySQL and ODBC, including Microsoft Office applications (including
>> Access), Crystal Reports, ADO and OleDB.
>>
>> With this release we're asking the user community to give detailed
>> feedback on which applications do not work with the driver, as we don't
>> have access to all possible combinations of MDAC, Microsoft Office
>> service pack and hotfix combinations for our own internal testing. We're
>> also especially interested in results from testing in-house or
>> commercial applications that don't have widespread availability.
>
>
> Guys. First of all: congratulations with this new release, it is
> another step forward. But... I'd like to know how much of a step. I
> see 19 verified bugs in the ODBC section that name 5.0. Some of them
> are obviously 3.51 related, but at least two are mine and thus 5.0.4.
> One of those two still pertains in this new version (even if it was
> reported back in July), given the new bug report 23375.
> As I have said before: I am happy to go bug-hunting, but I see not
> much feedback on this. I have not seen any progress report (neither in
> the list, nor in the publication of the new version and not even in
> the buglist) and this new version clearly still contains at least one
> older bug. My other bug described the problem of not being able to
> call stored procedures, which for me is rather important. Does 5.0.5
> solve #20963? If not, then installing it (for me) is useless.
>
> Once again: I admire your work and I know this is an open source
> project. The only thing I am stressing is that the (at least my)
> willingness to participate is heavily correlated with the amount of
> feedback and sense of being heard.
>
> Regards,
>
> Frank
>

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

Re: MySQL Connector/ODBC 5.0.5 has been released

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mogens Lunde wrote:
> I tried at the last release and also this one, but has never got any
> further than to trying to create an ODBC connection: Crash #¤#"%&!!
>
> "odbcad32.exe has encountered a problem ans needs to close. We are sorry
> for the inconvenience"
> AppName: odbcad32.exe AppVer: 3.525.1117.0 ModName: Unknown, ModVer:
> 0.0.0.0 OffSet: 00c14220-
> And then a one kilometer long error report where you can't copy/paste from.
>
> Seems to me as if this product is not nearly ready for beta testing.

Mogens,

What exact versions of Windows and MDAC are you running (since all
you're doing is trying to create a DSN from control panel)? We've been
creating DSNs (well, user ones, because of a longstanding bug) all over
the place for testing and debugging and haven't run into this issue.

I'd like to be able to reproduce your bug, but I haven't been able to
with the configurations available to me.

-Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)

iD8DBQFFNS+RtvXNTca6JD8RAh6tAJ4jL5/fh0h0QeKGpsnRWEtt52pPEACf Q82A
Cgm7gdjvNFYABfD8x0knS7U=
=JAOC
-----END PGP SIGNATURE-----

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

Re: MySQL Connector/ODBC 5.0.5 has been released

Mark Matthews wrote:

> Hello ODBC Users,
>
> Connector/ODBC v5.0.5 (the first BETA release) has been released.
>
....
> The driver is feature complete, and has started going through internal
> testing. At this time it is known to be able to link tables in Microsoft
> Access and perform some ADO-related functionality.

I've just installed this driver ( run batch script 'Install 0' ). I have
a number of problems ...

Firstly, I set up a new *System* DSN ( because this has traditionally
been the only type of connection I could make work ), but it didn't
appear in the ODBC manager under 'System DSN' ... it appeared under
'User DSN'. At the moment, I consider this problem to be merely
cosmetic, but could be causing other problems down the line.

Next, I go to MS Access, link tables, select the new DSN, select a
table, and get the error:

> Reserved error (-7749); there is no message for this error. [ OK / Help ]

If I instead try to link a view, I get:

> The Microsoft Jet database engine could not find the object
> 'VIEW_NAME'. Make sure the object exists and that you spell its name
> and the path name correctly.

I haven't bothered making ODBC trace log thingy yet, but can if someone
wants them.

I'm using:

- Windows 2000 SP4 and all Windows Updates
- MS Office XP ( Access 2002 ) with SP3
- MDAC 2.8
- msjet40.dll 4.0.8618.0
- MySQL-5.0.22

--
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak@nusconsulting.com.au
website: http://www.nusconsulting.com.au

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

Re: MySQL Connector/ODBC 5.0.5 has been released

Daniel -

We are aware of both issues and we're working to get them fixed.

--
Jess Balint, Developer
MySQL Inc, www.mysql.com
Office: +1 773 915 3175

On Mon, Oct 23, 2006 at 11:39:36AM +1000, Daniel Kasak wrote:
> Firstly, I set up a new *System* DSN ( because this has traditionally
> been the only type of connection I could make work ), but it didn't
> appear in the ODBC manager under 'System DSN' ... it appeared under
> 'User DSN'. At the moment, I consider this problem to be merely
> cosmetic, but could be causing other problems down the line.
>
> Next, I go to MS Access, link tables, select the new DSN, select a
> table, and get the error:
>
> >Reserved error (-7749); there is no message for this error. [ OK / Help ]
>
> If I instead try to link a view, I get:
>
> >The Microsoft Jet database engine could not find the object
> >'VIEW_NAME'. Make sure the object exists and that you spell its name
> >and the path name correctly.
>
> I haven't bothered making ODBC trace log thingy yet, but can if someone
> wants them.
>
> I'm using:
>
> - Windows 2000 SP4 and all Windows Updates
> - MS Office XP ( Access 2002 ) with SP3
> - MDAC 2.8
> - msjet40.dll 4.0.8618.0
> - MySQL-5.0.22
>
> --
> Daniel Kasak
> IT Developer
> NUS Consulting Group
> Level 5, 77 Pacific Highway
> North Sydney, NSW, Australia 2060
> T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
> email: dkasak@nusconsulting.com.au
> website: http://www.nusconsulting.com.au

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

Re: MySQL Connector/ODBC 5.0.6 BETA has been released

------=_NextPart_000_0001_01C6FF36.188516D0
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: 7bit

Dear Jess, Mark (and all),

Firstly: thanks for the much improved communication and regular releases of
MyODBC. I think we're all grateful to hear what's going on and get our teeth
into testing releases.

Further to Daniel Kasak's problem with 5.0.5, I have a similar issue with
5.0.6 BETA.

- XP Home SP2
- AMD Athlon XP
- 1GB RAM
- Office Professional 2003
- MDAC 2.8 SP1 (see attached file from Microsoft's MDAC checker)

I can correctly set up a system DSN now (ie the System-DSN-becomes-User-DSN
problem is fixed for me in 5.0.6b) but Access 2003, when asked to link
tables via a 5.0.6 DSN, gives:

Reserved Error (-7711); there is no message for this error.
[OK]

The Linked Table Manager then stops trying to link further tables.

I get the same error if I try to run a pass-through query using the v5.0.6b
DSN.

I knew how to set up logging on 3.51.12 but as there's no flag for it on the
5.0.6b DSN setup form I don't know how to log more information with this
release. If you need to know more, please provide instructions on how I can
find out what you need to know (I'm afraid I can't compile a debug build
from source files if that's what's required - I simply don't have the time
or expertise).

Regards,

Al McNicoll
Integritec Limited


-----Original Message-----
From: Jess Balint [mailto:jbalint@mysql.com]
Sent: 23 October 2006 04:51
To: Daniel Kasak
Cc: myodbc@lists.mysql.com
Subject: Re: MySQL Connector/ODBC 5.0.5 has been released

Daniel -

We are aware of both issues and we're working to get them fixed.

--
Jess Balint, Developer
MySQL Inc, www.mysql.com
Office: +1 773 915 3175

On Mon, Oct 23, 2006 at 11:39:36AM +1000, Daniel Kasak wrote:
> Firstly, I set up a new *System* DSN ( because this has traditionally
> been the only type of connection I could make work ), but it didn't
> appear in the ODBC manager under 'System DSN' ... it appeared under
> 'User DSN'. At the moment, I consider this problem to be merely
> cosmetic, but could be causing other problems down the line.
>
> Next, I go to MS Access, link tables, select the new DSN, select a
> table, and get the error:
>
> >Reserved error (-7749); there is no message for this error. [ OK / Help ]
>
> If I instead try to link a view, I get:
>
> >The Microsoft Jet database engine could not find the object
> >'VIEW_NAME'. Make sure the object exists and that you spell its name
> >and the path name correctly.
>
> I haven't bothered making ODBC trace log thingy yet, but can if someone
> wants them.
>
> I'm using:
>
> - Windows 2000 SP4 and all Windows Updates
> - MS Office XP ( Access 2002 ) with SP3
> - MDAC 2.8
> - msjet40.dll 4.0.8618.0
> - MySQL-5.0.22
>
> --
> Daniel Kasak
> IT Developer
> NUS Consulting Group
> Level 5, 77 Pacific Highway
> North Sydney, NSW, Australia 2060
> T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
> email: dkasak@nusconsulting.com.au
> website: http://www.nusconsulting.com.au


--
No virus found in this outgoing message.
Checked by AVG.
Version: 7.5.431 / Virus Database: 268.13.25/515 - Release Date: 03/11/2006
05:15



------=_NextPart_000_0001_01C6FF36.188516D0
Content-Type: text/xml;
name="MDAC versions.xml"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="MDAC versions.xml"

MDAC 2.8 SP1 ON WINDOWS XP SP2"> ON WINDOWS XP SP2" count=3D"13"> xmlns=3D"http://tempuri.org/CCFilestream_template.xsd" =
name=3D"MSADCOR.DLL" dir=3D"%COMMONFILES%\system\msadc\" =
CoreFile=3D"Yes">
version=3D"2.81.1117.0" fileversion=3D"2.81.1117.0"/>
Services Data Control Resources" date=3D"08/4/2004" =
fileVersion=3D"2.81.1117.0 (xpsp_sp2_rtm.040803-2158)" size=3D"16384" =
version=3D"2.81.1117.0"/>
name=3D"msado15.dll" dir=3D"%COMMONFILES%\system\ado\" CoreFile=3D"Yes">
version=3D"2.81.1117.0" fileversion=3D"2.81.1117.0"/>
Data Objects" date=3D"08/4/2004" fileVersion=3D"2.81.1117.0 =
(xpsp_sp2_rtm.040803-2158)" size=3D"536576" =
version=3D"2.81.1117.0"/>
name=3D"MSADOMD.DLL" dir=3D"%COMMONFILES%\system\ado\" CoreFile=3D"Yes">
version=3D"2.81.1117.0" fileversion=3D"2.81.1117.0"/>
Data Objects (Multi-Dimensional)" date=3D"08/4/2004" =
fileVersion=3D"2.81.1117.0 (xpsp_sp2_rtm.040803-2158)" size=3D"180224" =
version=3D"2.81.1117.0"/>
name=3D"msadrh15.dll" dir=3D"%COMMONFILES%\system\ado\" =
CoreFile=3D"Yes">
version=3D"2.81.1117.0" fileversion=3D"2.81.1117.0"/>
Data Objects Rowset Helper" date=3D"08/4/2004" =
fileVersion=3D"2.81.1117.0 (xpsp_sp2_rtm.040803-2158)" size=3D"57344" =
version=3D"2.81.1117.0"/>
name=3D"MSDASC.DLL" dir=3D"%COMMONFILES%\system\ole db\" =
CoreFile=3D"Yes">
version=3D"2.81.1117.0" fileversion=3D"2.81.1117.0"/>
Service Components Stub" date=3D"08/4/2004" fileVersion=3D"2.81.1117.0 =
(xpsp_sp2_rtm.040803-2158)" size=3D"4096" =
version=3D"2.81.1117.0"/>
name=3D"MSDASQL.DLL" dir=3D"%COMMONFILES%\system\ole db\" =
CoreFile=3D"Yes">
version=3D"2.81.1117.0" fileversion=3D"2.81.1117.0"/>
Provider for ODBC Drivers" date=3D"08/4/2004" fileVersion=3D"2.81.1117.0 =
(xpsp_sp2_rtm.040803-2158)" size=3D"315392" =
version=3D"2.81.1117.0"/>
name=3D"MSDASQLR.DLL" dir=3D"%COMMONFILES%\system\ole db\" =
CoreFile=3D"Yes">
version=3D"2.81.1117.0" fileversion=3D"2.81.1117.0"/>
Provider for ODBC Drivers Resources" date=3D"08/4/2004" =
fileVersion=3D"2.81.1117.0 (xpsp_sp2_rtm.040803-2158)" size=3D"16384" =
version=3D"2.81.1117.0"/>
name=3D"OLEDB32.DLL" dir=3D"%COMMONFILES%\system\ole db\" =
CoreFile=3D"Yes">
version=3D"2.81.1117.0" fileversion=3D"2.81.1117.0"/>
Services" date=3D"08/4/2004" fileVersion=3D"2.81.1117.0 =
(xpsp_sp2_rtm.040803-2158)" size=3D"487424" =
version=3D"2.81.1117.0"/>
name=3D"SQLOLEDB.DLL" dir=3D"%COMMONFILES%\system\ole db\" =
CoreFile=3D"Yes">
version=3D"2000.85.1117.0" fileversion=3D"8.0.1117.0"/>
Server" date=3D"08/4/2004" fileVersion=3D"2000.085.1117.00 =
(xpsp_sp2_rtm.040803-2158)" size=3D"528384" =
version=3D"2000.85.1117.0"/>
name=3D"SQLSRV32.DLL" dir=3D"%SYSTEMDIR%\" CoreFile=3D"Yes">
version=3D"2000.85.1117.0" fileversion=3D"3.85.1117.0"/>
date=3D"08/4/2004" fileVersion=3D"2000.085.1117.00 =
(xpsp_sp2_rtm.040803-2158)" size=3D"442368" =
version=3D"2000.85.1117.0"/>
name=3D"msdart.dll" dir=3D"%SYSTEMDIR%" CoreFile=3D"Yes">
version=3D"2.81.1117.0" fileversion=3D"2.81.1117.0"/>
Runtime Routines" date=3D"08/4/2004" fileVersion=3D"2.81.1117.0 =
(xpsp_sp2_rtm.040803-2158)" size=3D"151552" =
version=3D"2.81.1117.0"/>
name=3D"msdaorar.dll" dir=3D"%COMMONFILES%\system\ole db\" =
CoreFile=3D"Yes">
version=3D"2.81.1117.0" fileversion=3D"2.81.1117.0"/>
Provider for Oracle Resources" date=3D"08/4/2004" =
fileVersion=3D"2.81.1117.0 (xpsp_sp2_rtm.040803-2158)" size=3D"16384" =
version=3D"2.81.1117.0"/>
name=3D"msorc32r.dll" dir=3D"%SYSTEMDIR%\" CoreFile=3D"Yes">
version=3D"2.575.1117.0" fileversion=3D"2.575.1117.0"/>
for Oracle Resources" date=3D"08/4/2004" fileVersion=3D"2.575.1117.0 =
(xpsp_sp2_rtm.040803-2158)" size=3D"20480" =
version=3D"2.575.1117.0"/>



------=_NextPart_000_0001_01C6FF36.188516D0
Content-Type: text/plain; charset=us-ascii


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=gcdmo-myodbc@m.gmane.org
------=_NextPart_000_0001_01C6FF36.188516D0--