--------------030808080906050601040800
Content-Type: multipart/alternative;
boundary="------------050905060300070804060709"
--------------050905060300070804060709
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Peter Harvey wrote:
> Thanks for the feedback on patch3! A few problems were reported and
> they have either been fixed or will be fixed.
>
> We are now looking for feedback on the next distribution. It can be
> obtained here;
>
> http://www.peterharvey.org/Downloads/MySQL/MyODBC/MyODBC-3.5 1.11-1-win.exe
>
>
> Thanks everyone!
I've just done some quick testing on 2 PCs, and both were better than
the 3.51.10 release, which crashed upon connecting, but there are still
some issues.
Most of the app ( which is in Access 2002 ) is simple forms based on
linked tables, and code which uses ADO to talk to MySQL. All this works
fine. However there is one part of the app where I was trying out using
an ADO connection to Access' linked tables ( I was having some issues
with DAO at one point, and thought I'd try this out ). Anyway, the code
was basically working until the upgrade from 3.51.09, and now it gives a
connection error which immediately crashes the runtime version of
Access. The developer version allows me to inspect slightly further:
?myconn.Errors (0)
ODBC--connection to 'NUS' failed.
?myconn.Errors (1)
Data provider failed while executing a provider command.
The code which triggered this error is very simple:
---
Dim myconn as ADODB.connection, myset as ADODB.recordset, sqlstr as string
Set myconn = New ADODB.connection
With myconn
.ConnectionString = CurrentProject.AccessConnection
.CursorLocation = adUseClient
End With
Set myset = New ADODB.Recordset
With myset
.ActiveConnection = myconn
.LockType = adLockReadOnly
End With
' Now some code builds a valid SQL string ... and then opens it:
myset.Open sqlstr
---
The code halts at this point. I've attached a zipped ODBC trace of
everything from opening the Access shell to triggering the error. I
don't know why it's so damned lengthy. Look right down the bottom of it
- I think this is where the error happens, but I don't know what I'm
looking at, so I'm only guessing.
As a side note, I was unable to make the MyODBC driver log to a text
file as advertised ( by clicking the 'log' option in the debug tab in
the connection setup ). Instead I used the 'Tracing' tab of the general
ODBC administrator in Win2k.
I have removed the single instance of using an ADO connection to Access,
and reverted to using DAO, and now the app is running ( on one PC for
further testing ).
--
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 [at] nusconsulting.com.au
website: http://www.nusconsulting.com.au
--------------050905060300070804060709
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Peter Harvey wrote:
<blockquote cite="mid41FA9236.7060609 [at] mysql.com" type="cite">Thanks for
the feedback on patch3! A few problems were reported and they have
either been fixed or will be fixed.
<br>
<br>
We are now looking for feedback on the next distribution. It can be
obtained here;
<br>
<br>
<a class="moz-txt-link-freetext" href="http://www.peterharvey.org/Downloads/MySQL/MyODBC/MyODBC-3.51.11-1-win.exe"> http://www.peterharvey.org/Downloads/MySQL/MyODBC/MyODBC-3.5 1.11-1-win.exe</a>
<br>
<br>
Thanks everyone!
<br>
</blockquote>
<br>
I've just done some quick testing on 2 PCs, and both were better than
the 3.51.10 release, which crashed upon connecting, but there are still
some issues.<br>
<br>
Most of the app ( which is in Access 2002 ) is simple forms based on
linked tables, and code which uses ADO to talk to MySQL. All this works
fine. However there is one part of the app where I was trying out using
an ADO connection to Access' linked tables ( I was having some issues
with DAO at one point, and thought I'd try this out ). Anyway, the code
was basically working until the upgrade from 3.51.09, and now it gives
a connection error which immediately crashes the runtime version of
Access. The developer version allows me to inspect slightly further:<br>
<br>
?myconn.Errors (0)<br>
ODBC--connection to 'NUS' failed.<br>
?myconn.Errors (1)<br>
Data provider failed while executing a provider command.<br>
<br>
The code which triggered this error is very simple:<br>
<br>
---<br>
<br>
Dim myconn as ADODB.connection, myset as ADODB.recordset, sqlstr as
string<br>
<br>
Set myconn = New ADODB.connection<br>
<br>
With myconn<br>
.ConnectionString = CurrentProject.AccessConnection<br>
.CursorLocation = adUseClient<br>
End With<br>
<br>
Set myset = New ADODB.Recordset<br>
<br>
With myset<br>
.ActiveConnection = myconn<br>
.LockType = adLockReadOnly<br>
End With<br>
<br>
' Now some code builds a valid SQL string ... and then opens it:<br>
<br>
myset.Open sqlstr<br>
<br>
---<br>
<br>
The code halts at this point. I've attached a zipped ODBC trace of
everything from opening the Access shell to triggering the error. I
don't know why it's so damned lengthy. Look right down the bottom of it
- I think this is where the error happens, but I don't know what I'm
looking at, so I'm only guessing.<br>
<br>
As a side note, I was unable to make the MyODBC driver log to a text
file as advertised ( by clicking the 'log' option in the debug tab in
the connection setup ). Instead I used the 'Tracing' tab of the general
ODBC administrator in Win2k.<br>
<br>
I have removed the single instance of using an ADO connection to
Access, and reverted to using DAO, and now the app is running ( on one
PC for further testing ).<br>
<div class="moz-signature"><br>
-- <br>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<title>sig</title>
Daniel Kasak
<br>
IT Developer
<br>
<span style="font-weight: bold;">NUS Consulting Group</span><br>
Level 5, 77 Pacific Highway<br>
North Sydney, NSW, Australia 2060
<br>
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
<br>
email: <a class="moz-txt-link-abbreviated"
href="mailto:dkasak [at] nusconsulting.com.au">dkasak [at] nusconsulti ng.com.au</a>
<br>
website: <a class="moz-txt-link-freetext"
href="http://www.nusconsulting.com.au">http://www.nusconsult ing.com.au</a>
</div>
</body>
</html>
--------------050905060300070804060709--
--------------030808080906050601040800
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 [at] m.gmane.org
--------------030808080906050601040800--
