DOC: "OLEDB_SERVICES = -2" Does Not Disable Autoenlistment (245267)

MORE INFORMATION

WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys and Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. If you are running Windows NT, you should also update your Emergency Repair Disk (ERD).

In the Microsoft Data Access SDK version 2.0 documentation you find the following paragraph: 4.4.5.1 Enabling/Disabling Services for a Provider

Individual OLE DB services can be enabled or disabled by default for all applications that access a single provider. This is done by adding an OLEDB_SERVICES registry entry under the provider's CLSID, with a DWORD value specifying the services to enable or disable as follows:

Default Services Enabled	Keyword Value
All services (the default)	0xffffffff
All except Pooling and AutoEnlistment	0xfffffffe
All except Client Cursor	0xfffffffb
All except pooling, enlistment, and cursor	0xfffffff0
No services	0x00000000
No aggregation, all services disabled	[missing key]

This information is not completely correct. It should read:

Default Services Enabled	Keyword Value
All services (the default)	0xffffffff = -1
All except Pooling	0xfffffffe = -2
All except Pooling and AutoEnlistment	0xfffffffc = -4
All except Client Cursor	0xfffffffb = -5
All except pooling, enlistment, and cursor	0xfffffff8 = -8
No services	0x00000000
No aggregation, all services disabled	[missing key]

The same values are true for the paragraph "4.4.5.2 Overriding Provider Service Defaults".

If you disable pooling you should always disable autoenlistment as well.