Microsoft Jet Database Engine Provider for OLE DB

The Microsoft Jet Database Engine Provider allows ADO to access any Jet database file, or any Jet installable ISAM desktop database file.

Connection String Parameters

Provider-Specific Properties

The Properties collections of the Connection, Command, and Recordset objects include dynamic properties specific to the provider. After establishing the connection and creating these objects, use the Refresh method on the object’s Properties collection to obtain the provider-specific properties.

These properties provide information about functionality specific to the provider beyond the built-in properties ADO supports.

The following tables describe the properties specific to the Microsoft Jet Database Engine Provider for OLE DB, listed by their ordinal position (or index) in the Properties collection. For more information about these properties, refer to ???.

Connection object properties specific to the Microsoft Jet Database Engine Provider for OLE DB:

(Conor - all the rest of the details that follow are for Kagera - I left them here to give you an example of what I’m looking for)

Index Property Name Index Property Name

Command and Recordset object properties specific to the Microsoft Jet Database Engine Provider for OLE DB:

Index Property Name Index Property Name

Recordset Limitations

The following tables list the features available with ADO Recordset objects of different cursor types when you use the Microsoft Jet Database Engine Provider for OLE DB. All cases assume a Recordset opened on an indexed table with LockType = adLockBatchOptimistic.

Supports method arguments:

ForwardOnly Dynamic Keyset Static
adAddNew True True True True
adApproxPosition False False False False
adBookmark False False True True
adDelete True True True True
adHoldRecords False False True True
adMovePrevious False True True True
adResync False False True True
adUpdate True True True True
adUpdateBatch True True True True

Recordset properties:

ForwardOnly Dynamic Keyset Static
AbsolutePage not available not available write-only write-only
AbsolutePosition not available not available write-only write-only
ActiveConnection read/write read/write read/write read/write
BOF read-only read-only read-only read-only
Bookmark not available not available read/write read/write
CacheSize read/write read/write read/write read/write
CursorType read/write read/write read/write read/write
EditMode read-only read-only read-only read-only
EOF read-only read-only read-only read-only
Filter read/write read/write read/write read/write
LockType read/write read/write read/write read/write
MaxRecords read/write read/write read/write read/write
PageCount not available not available read-only read-only
PageSize read/write read/write read/write read/write
RecordCount not available not available read-only read-only
Source read/write read/write read/write read/write
Status read-only read-only read-only read-only

Recordset methods:

ForwardOnly Dynamic Keyset Static
AddNew Yes Yes Yes Yes
CancelUpdate Yes Yes Yes Yes
CancelBatch Yes Yes Yes Yes
Clone No No Yes Yes
Close Yes Yes Yes Yes
Delete Yes Yes Yes Yes
GetRows Yes Yes Yes Yes
Move Yes Yes Yes Yes
MoveFirst Yes Yes Yes Yes
MoveLast No No Yes Yes
MovePrevious No Yes Yes Yes
Open Yes Yes Yes Yes
Requery Yes Yes Yes Yes
Resync No No Yes Yes
Supports Yes Yes Yes Yes
Update Yes Yes Yes Yes
UpdateBatch Yes Yes Yes Yes

Notes:

While it is possible to request batch updating in conjuction with forward-only and dynamic cursors, you are currently prevented from updating more than one row at a time. You should therefore only use batch updating with keyset and static cursors, i.e. where both rstTemp.Supports(adUpdateBatch) and rstTemp.Supports(adHoldRecords) are True.

Error Messages

For infomation about error messages generated by the Microsoft Jet Database Engine Provider for OLE DB, see the Microsoft Jet Error Message Reference.


© 1997 Microsoft Corporation. All rights reserved. Terms of Use.