List:MySQL ODBC« Previous MessageNext Message »
From:Al McNicoll Date:November 3 2006 10:52am
Subject:Re: MySQL Connector/ODBC 5.0.6 BETA has been released
View as plain text  
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
- 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.

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

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).


Al McNicoll
Integritec Limited

-----Original Message-----
From: Jess Balint [mailto:jbalint@stripped] 
Sent: 23 October 2006 04:51
To: Daniel Kasak
Cc: myodbc@stripped
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,
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@stripped
> website:

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

Attachment: [text/xml] MDAC versions.xml
Attachment: [text/xml] MDAC versions.xml
MySQL Connector/ODBC 5.0.5 has been releasedMark Matthews17 Oct
  • Re: MySQL Connector/ODBC 5.0.5 has been releasedFrank Maas17 Oct
    • Re: MySQL Connector/ODBC 5.0.5 has been releasedMogens Lunde17 Oct
  • Re: MySQL Connector/ODBC 5.0.5 has been releasedDaniel Kasak23 Oct
    • Re: MySQL Connector/ODBC 5.0.5 has been releasedJess Balint23 Oct
      • Re: MySQL Connector/ODBC 5.0.6 BETA has been releasedAl McNicoll3 Nov