Posted Date: February 6, 1995

Go To TechNet Home Page

ODBC Driver Pack 2.0 Fulfillment Kit Q&A

Which drivers ship in the box?

16- and 32- bit drivers for the following data sources are provided in this package:

• Microsoft Access 1.x and 2.0
• Microsoft FoxPro 2.0, 2.5 and 2.6
• dBASE III and IV
• Paradox 3.x and 4.x
• Btrieve (16-bit only)
• Microsoft Excel 3, 4 and 5
• Text
• Oracle 6 and 7* (16-bit only)
• SQL Server 4.2x*

*These drivers ship with the fulfillment kit only.

Who can purchase the fulfillment kit and how much does it cost?

For customers of Microsoft products, we are charging $10.25 to cover the cost of materials and shipping. A customer must own one of the following products:

• Word
• Excel
• Microsoft Office or Office Professional
• ODBC Drivers Fulfillment Kit version 1.0
• Microsoft Access 2.0
• FoxPro 2.6
• ODBC Desktop Drivers version 1.0
• Visual Basic 3.0
• Visual C++ through 2.0

What's new in this package?

• Support for these additional data sources: Oracle 7, Excel 5, Access 2, FoxPro 2.6, Paradox 4.x, and 32-bit support for SQL Server 4.2.
• Compliant with ODBC version 2.01 specification.
• Users can call stored queries in Access the same manner they would use tables.
• Users can attach to named ranges in an Excel worksheet.
• Support for scrollable cursors.
• Transactions are supported against Access, SQL Server, and Oracle data.
• Support for updateable joins.
• Based on a 32-bit version of the Jet engine (version 2.5).
• Improved performance.
• Support for stored queries or stored procedures.
• The Desktop drivers support positioned cursor operations natively (via SQLSetPos)

What are the changes in functionality between the version 1 drivers and these?

In addition to the new features outlined above, please see the Help file (odbcjtnw.hlp) for a list of differences.

My company has lots of workstations that need this software. Do I need to purchase lots of copies of the fulfillment kit?

The license in the fulfillment kit allows you to install the drivers onto any workstation that has a valid license for Word, Excel, Access, FoxPro, Visual Basic, Visual C or the single-user ODBC Desktop Driver Pack version 1.0. You need to purchase only one copy of the fulfillment kit to install it on any of these machines.

I developed an application using VBA in Excel and the pre-release Access 2.0 driver. I understand that this driver did not ship with the early releases of Excel 5.0. May I ship the driver with my VBA app?

The early ODBC Driver for Access shipped with only Excel 5.0c. The license in this package allows you to ship the Access 2.0 ODBC driver with your VBA application as long as the target workstation has a valid license for Word or Excel.

Can I use the new Access 2.0 driver with 1.0 or 1.1 data?

Yes. This new driver supports all versions of Access data.

Is this the same version of Jet that ships with Access 2.0?

No. This product includes version 2.5 of Microsoft's Jet database engine. However, this engine is will work seamlessly with Access 2.0 and VB 3.0 using the Visual Basic Compatibility Layer.

Can I use the 16-bit drivers from 32 bit apps?

Under Windows for Workgroups, 32-bit Win32s apps can use 16-bit drivers. Under Windows NT, 16-bit apps can use 16- or 32-bit drivers and 32-bit apps can only use 32-bit drivers.

What version of Windows NT do I need to run the desktop drivers?

You must use Windows/NT version 3.5 for the desktop drivers. The SQL Server and Oracle drivers can run on Windows NT 3.1 or 3.5.

Can I use the desktop drivers with Windows 95?

Since Windows 95 is not a released operating system, the drivers are not guaranteed to work with it. Future versions of the drivers will be Windows 95-compliant.

Does the Oracle 7 driver work with Oracle 6?

The Oracle 7 driver only works with Oracle 7.

Does the Oracle 6 driver work with Oracle 7?

Yes, but you cannot take advantage of the new features in Oracle 7.

What's the conformance levels for these drivers?

API = Level 1 with lots of level 2 implemented.

SQL = Minimum.

Does the ODBC Driver Pack support "SQL extended fetch"?

The desktop drivers support the level 2 ODBC API call SQLExtendedFetch. The other drivers support SQLExtendedFetch through use of the cursor library.

What languages will the drivers be available in?

• German
• French
• Italian
• Swedish
• Dutch
• Spanish
• Danish
• Norwegian
• Portuguese
• Finnish

Go To TechNet Home Page

Go To Microsoft Home Page