fixed table to match two other similar tables on docs

mikeblome · mikeblome · commit 1e8f4b540e21 · 2019-07-30T17:19:23.000-07:00
diff --git a/docs/data/oledb/enabling-and-disabling-services-for-a-provider.md b/docs/data/oledb/enabling-and-disabling-services-for-a-provider.md
@@ -1,22 +1,23 @@
 ---
 title: "Enabling and Disabling Services for a Provider"
-ms.date: "10/29/2018"
+ms.date: "07/30/2019"
 helpviewer_keywords: ["OLE DB services [OLE DB], enabling and disabling", "service providers [OLE DB]"]
 ms.assetid: 3deac1bb-f660-407a-92ef-95e139e280c0
 ---
 # Enabling and 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 shown in the following table.
 
-|Default services enabled|Keyword value|
+|Default services enabled|DWORD value|
 |------------------------------|-------------------|
+|All services except client cursor and pooling|0xfffffffa|
+|All services except Client Cursor|0xfffffffb|
+|All services except Pooling and AutoEnlistment|0xfffffffc|
+|All services except pooling|0xfffffffe|
 |All services (default)|0xffffffff|
-|All except Pooling and AutoEnlistment|0xfffffffe|
-|All except Client Cursor|0xfffffffb|
-|All except Pooling, AutoEnlistment, and Client Cursor|0xfffffff0|
 |No services|0x00000000|
-|No aggregation, all services disabled|\<missing key>|
+|No aggregation, all services disabled|No OLEDB_Services registry entry|
 
 ## See also
 
-[Enabling and Disabling OLE DB Services](../../data/oledb/enabling-and-disabling-ole-db-services.md)
+[Enabling and Disabling OLE DB Services](../../data/oledb/enabling-and-disabling-ole-db-services.md)
