Important:
This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
A version of this page is also available for
4/8/2010

This function removes a format enumerator from the given bind context.

Syntax

HRESULT RevokeFormatEnumerator(
  LPBC 
pbc,
  IEnumFORMATETC* 
pEFetc
);

Parameters

pbc

[in] Address of the IBindCtxinterface for the bind context from which the enumerator is to be revoked.

pEFetc

[in] Address of the IEnumFORMATETCinterface for the enumerator to revoke.

Return Value

Returns S_OK if the enumerator was successfully removed or E_INVALIDARG if one or more parameters are invalid.

Remarks

This function removes a format enumerator from the bind context specified in pbc. It must previously have been registered with a call to RegisterFormatEnumerator.

Note:
It is not necessary to make this call for every use of a bind context. It is possible, although not recommended, to reuse the same bind context and the same format enumerator for several bind operations. Upon calling Release, all registered objects on that bind context are revoked, including the format enumerator interfaces. Therefore, releasing a bind context implicitly releases all registered format enumerators. However, if you choose to reuse a bind context, you can use RevokeFormatEnumeratorto remove a registered format enumerator so it is not reused.

Requirements

Header urlmon.h, urlmon.idl
Library urlmon.lib
Windows Embedded CE Windows CE .NET 4.0 and later
Windows Mobile Windows Mobile Version 5.0 and later
500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.