Initializing the Microsoft Exchange Data Source Driver
When you install the Microsoft® Exchange Data Source driver, the Setup program writes a set of default values to the Microsoft Windows® Registry in the Engines and ISAM Formats subkeys. You should not modify these settings directly; use the setup program for your application to add, remove, or change these settings. The following sections describe initialization and ISAM Format settings for the Microsoft Exchange Data Source driver.
Microsoft Exchange Data Source Initialization Settings
The Jet\4.0\Engines\Exchange folder includes initialization settings for the msexch40.dll driver, used for external access to Microsoft Outlook and Microsoft Exchange folders. The only entry in this folder is the following:
win32=<path>\msexch40.dll
The Microsoft Jet database engine uses this setting to indicate the location of msexch40.dll. The full path is determined at the time of installation.
The results of using the Outlook ISAM format and of using the Exchange client ISAM format are similar. The only difference is that the two different clients use different names for the same columns. The two ISAM formats have been created so that Microsoft Jet can return the column names in the particular style that the user desires.
Microsoft Outlook Client ISAM Formats
The Jet\4.0\ISAM Formats\Exchange 9.0 folder contains the following entries.
Entry name |
Type |
Value |
|
|---|---|---|---|
| Engine | REG_SZ | Exchange | |
| ImportFilter | REG_SZ | Outlook() | |
| CanLink | REG_BINARY | 01 | |
| OneTablePerFile | REG_BINARY | 00 | |
| IsamType | REG_DWORD | 3 | |
| IndexDialog | REG_BINARY | 00 | |
| CreateDBOnExport | REG_BINARY | 00 | |
| SupportsLongNames | REG_BINARY | 01 |
Note When you change Windows Registry settings, you must exit and then restart the database engine for the new settings to take effect.
Microsoft Exchange Client ISAM Formats
The Jet\4.0\ISAM Formats\Exchange 4.0 folder contains the following entries.
Entry name |
Type |
Value |
|
|---|---|---|---|
| Engine | REG_SZ | Exchange | |
| ImportFilter | REG_SZ | Exchange() | |
| CanLink | REG_BINARY | 01 | |
| OneTablePerFile | REG_BINARY | 00 | |
| IsamType | REG_DWORD | 3 | |
| IndexDialog | REG_BINARY | 00 | |
| CreateDBOnExport | REG_BINARY | 00 | |
| SupportsLongNames | REG_BINARY | 01 |
Note When you change Windows Registry settings, you must exit and then restart the database engine for the new settings to take effect.
Customizing the Schema.ini File for Outlook and Exchange Data
The Schema.ini file is used by the Outlook and Exchange ISAM in much the same way that it is used by the Text ISAM. Schema.ini contains the specifics of a data source: how the data is formatted, and the names of columns that should be accessed.
It is not necessary to modify the Schema.ini file before data can be read, imported, or exported for Outlook and Exchange. Many of the settings inside the Schema.ini file for Outlook and Exchange are specific to internal tags that MAPI requires. You should not attempt to modify those tag values.
See Also
Customizing Windows Registry Settings for Microsoft Jet