[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql-odbc
Subject:    RE: myodbc: Access 2.0
From:       Bill Adams <badams () tqs ! com>
Date:       1998-03-06 19:04:49
[Download RAW message or body]

Thank you.  That was the trick.   One change in Info.c and it works with
Access 2.0.  Thank you.  Thank you. And thanks again.

There were problems compiling 2.50.11, but I will send that to the
entire list.

--Bill


>----------
>From: 	Michael Widenius[SMTP:monty@tcx.se]
>Sent: 	Friday, March 06, 1998 8:18 AM
>To: 	Bill Adams
>Cc: 	'MyODBC'
>Subject: 	myodbc: Access 2.0
>
>>>>>> "Bill" == Bill Adams <badams@tqs.com> writes:
>
>Bill> Hello.  Right now, most of my company is stuck using Access 2.0 in NT.
>Bill> When I try to link a table:
>
>File-> Attach Table... -> <SQL Database> -> MFG via MySQL (that is my
>Bill> datasource name) -> test_x (the table name) -> 
>
>Bill> I get an "ODBC Specification Conformance Error (-7761)".
>
>Bill> I have attached myodbc.log and sql.log.
>
>Bill> The same setup with Access 7.0 works great.
>
>Bill> Thanks for your time.
>
>
>From the log it seams that Access asks if MySQL supports outer joins.
>MySQL respones with 'F'  = FULL which is the correct answer according
>to ODBC 2.0.
>
>The problem may be that the ODBC 1.0 specification only had the values
>'Y' and 'N' and Access 2.0 isn't ODBC upwards compatible.  According
>to the ODBC 2.5 manual the change in ODBC 2.0 is upward compatible
>for all ODBC compliant programs.
>
>If you are stuck with Access 2.0 you can always get the MyODBC source
>and try to change the MyODBC driver to be Access 2.0 compliant.
>If you have VC++ this should be relatively easy.  If this is real
>important you can always ask for an offer about this.  We only have to
>get hold on an Access 2.0 copy somewhere...
>
>Yours,
>Monty
>

[prev in list] [next in list] [prev in thread] [next in thread]