Re: ODBC - Access 2.0 -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

If you are using a 32 bit driver with client access it will not work. 
Access 2.0 will only import with a 16 bit client access driver.  So either
upgrade to Access 97 or use a client access version with the 16bit drivers.

----------
You Wrote: 
> 
> I am testing the new Enhanced Client Access for win 3.1. The ODBC driver
> works fine with the database access tool that is provided with Client
> Access. When I uses ODBC with Microsoft Access 2.0 it retrieves the
> tables list fine but when I try to import a table I get an "ODBC
> Specification Conformance Error[-7761]." I am using TCP/IP with OS/400
> V3R7.
> 

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.