hello peter,
the nmake-issue seems to be fixed. debug and release can be built again =
(with nmake).
i noticed that the current bitkeeper debug-build is missing the =
trace-support:
I patched makefine.ini:
# debug flags
DEBUG_CFLAGS =3D -DDBUG_ON -D_DBUG_ON -DDEBUG -D_DEBUG =
-DLOG_ALL
~~~~~~~~~~
but this patch creates only 'myodbc.log' and not myodbc.sql.
Anyway the myodbc3d.dll contained in your recent msi-distrib. logs as =
exspected.
Your current release works well for us (both access and odbc-api).
regards,armin.
> -----Original Message-----
> From: Peter Harvey [mailto:pharvey [at] mysql.com]
> Sent: Monday, January 31, 2005 1:50 AM
> To: myodbc [at] lists.mysql.com
> Subject: Re: MyODBC-3.51.11-1-win
>
> Daniel,
>
> I just created a revised 3.51.11-1 distro which will be good
> for another round of builds and an official release. Can you
> please create a bug for this problem and attach all of this,
> very useful, information to it?
> Doing so will ensure that you are notified of the progress in
> getting it fixed and make you the person who decides if the
> bug can be closed.
>
> Thanks a lot!
>
> Peter
>
> Daniel Kasak wrote:
>
> > 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-wi
> >> n.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 =3D New ADODB.connection
> >
> > With myconn
> > .ConnectionString =3D CurrentProject.AccessConnection
> .CursorLocation
> > =3D adUseClient End With
> >
> > Set myset =3D New ADODB.Recordset
> >
> > With myset
> > .ActiveConnection =3D myconn
> > .LockType =3D 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
>
>
>
> --
> Peter Harvey, Software Developer
> MySQL AB, www.mysql.com
>
> Are you MySQL certified? www.mysql.com/certification
>
>
>
> --
> MySQL ODBC Mailing List
> For list archives: http://lists.mysql.com/myodbc
> To unsubscribe:
> http://lists.mysql.com/myodbc?unsub=3Darmin.schoeffmann [at] aega eon.de
>
>
>
>
--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe: http://lists.mysql.com/myodbc?unsub=3Dgcdmo-myodbc [at] m.gmane.o rg
