(c) 1998 Microsoft Corporation. All rights reserved.
This document provides late-breaking or other information that supplements the Microsoft OLE DB Provider for Jet documentation.
--------
CONTENTS
--------
1. PRODUCT DESCRIPTION
2. NEW FEATURES
3. TECHNICAL NOTES
4. KNOWN BUGS, LIMITATIONS, AND WORKAROUNDS
----------------------
1. PRODUCT DESCRIPTION
----------------------
The Microsoft OLE DB Provider for Jet is a native OLE DB provider for data stored in the .mdb file format used by Microsoft Access. With this native OLE DB provider you no longer have to rely on the Microsoft Access ODBC Driver to read and write data in a Microsoft Access database.
---------------
2. NEW FEATURES
---------------
With this release of the Microsoft OLE DB Provider for Jet you can use ANSI standard syntax with respect to parameter markers in queries. Previous versions of this provider supported only the Microsoft Jet-specific parameter marker syntax consisting of a parameter name enclosed in square brackets, where the parameter name is optional.
Example: parameters parm1 text; select * from Table1 WHERE col1 = [parm1];
This version of the provider also supports the ANSI syntax where a question mark, "?", is the parameter marker, ex. "...WHERE col1 = ?".
Also with this release of the Microsoft OLE DB Provider for Jet, Jet-specific syntax for wildcards ("*" and "?") has been replaced by ANSI syntax for wildcards ("%" and "_"). For example, want to run a query that would return all instances of where the data for a column started with the letter "A". Previously, the restriction which would have be written "...WHERE col1 LIKE("A*")" would now be written "...WHERE col1 LIKE("A%")". Please note that queries using the older, non-ANSI syntax will no longer return the same set of rows.
------------------
3. TECHNICAL NOTES
------------------
If you have previously created OLE DB applications to access your Microsoft Access .mdb files, your applications used the Microsoft Access ODBC Driver. However, you may now be able to create more efficient applications with the Microsoft OLE DB Provider for the Microsoft Access Jet database engine.
With the new functionality provided by the Microsoft OLE DB Provider for Jet, you can bypass the Open Database Connectivity (ODBC) layer when accessing your Microsoft Access database files. This means that you do not need to create a Data Source Name (DSN) file, which ODBC uses for mapping data sources to underlying database software.
To connect to a Microsoft Access database, you previously had to create and reference a DSN in your scripts. For example, the following script establishes a connection with a Microsoft Access database:
Set cnnConn = Server.CreateObject("ADODB.Connection")
However, with the Microsoft OLE DB Provider for Jet, you can directly access your Microsoft Access database files. The following opens a database connection without referencing a DSN:
Your applications that use the Microsoft Access ODBC Driver will continue to be supported. However, you may choose to convert your existing applications from the Microsoft Access ODBC Driver to the Microsoft OLE DB Provider for Jet.
If you need to access secure databases through the Microsoft OLE DB Provider for Jet, you may have to set additional information than what is listed above. To specify a database password (as opposed to a user password), you need to set the property "Jet OLEDB:Database Password" on the ADO connection object (as above). Furthermore, if you need to specify a specific system database, you should use the property "Jet OLEDB:System database".
Please note that the default mode for opening databases in the Microsoft OLE DB Provider for Jet is read/write. If your .mdb file is on a read-only file system, you will get a failure if you try to open the database using the default settings. You can only open these databases in the read-only mode.
-----------------
4. KNOWN BUGS, LIMITATIONS, AND WORKAROUNDS
-----------------
If you choose to convert your applications, you must be aware of the functionality differences between the two providers' access methods. Specifically, for this release, the Microsoft OLE DB Provider for Jet does not support the following:
* The ODBC specified canonical syntax for invoking intrinsic functions.
* Access to databases or files other than native Microsoft Jet databases (e.g. Excel, dBase, Text, etc.) via Microsoft Jet installable ISAMs.
* The ability to create stored queries, sometimes referred to as stored procedures.
Installable ISAM Support
There is currently no support for accessing data other than native Jet data when using the Microsoft OLE DB Provider for Jet directly. If it is imperative that you access external data from your application you can, and should, continue to use the Microsoft OLE DB Provider for ODBC until the next release of the Microsoft OLE DB Provider for Jet. This provider will be available with the MDAC 2.1 release.
Stored Procedure Support
Stored Procedures must first be created in Access as Querydefs to be exercised by the Microsoft OLE DB Provider for Jet. There is no facility to create the stored procedures directly from code for this release.
The following is a list of Microsoft OLE DB Provider for Jet 3.52 known bugs.
IRowsetUpdate::GetOriginalData will fail on a newly inserted row while change is pending.
IRowsetUpdate::GetOriginalData will fail on a newly inserted row while the pending change is outstanding. The Jet 3.5 Engine itself will not handle the case where you try to retrieve the original values for a newly inserted columns, hence the OLE DB provider cannot support this functionality.
Adding new records through ADO Client Cursor returns E_FAIL.
If you are using the ADO Client Cursor (Recordset.CursorLocation = adUseClient) to add new records to a Jet database through the Microsoft OLE DB Provider for Jet and do not set values for each of the columns in the table, the provider will return E_FAIL with the message "Number of query values and destination columns aren't the same". To avoid the error, do not use the Client Cursor.
Another scenario where this error will occur is on a parameterized INSERT INTO query that adds a record to a Jet database through the Microsoft OLE DB Provider for Jet. The error occurs if the query does not set each of the columns of the table. For example, if a table has two columns and you want to set only one of them, you would typically use the following query: INSERT INTO T1 (c1) SET (?). This, however, will fail. You would have to use something like the following instead: INSERT INTO T1 (c1, c2) SET (?, NULL) or INSERT INTO T1 (c1, c2) SET (?, "FOO"), giving an explicit value for the column c2.
