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 method numerates the next cConnections elements (for example, CONNECTDATAstructures) in the enumerator's list, returning them in rgpcdalong with the actual number of enumerated elements in pcFetched.

The caller is responsible for calling CONNECTDATA .pUnk->Releasefor each element in the array when this method returns successfully.

If cConnectionsis greater than one, the caller must also pass a non-NULL pointer to pcFetchedto get the number of pointers it has to release.

Syntax

HRESULT Next(
  ULONG 
cConnections, 
  CONNECTDATA** 
rgpcd, 
  ULONG* 
pcFetched	 
);

Parameters

cConnections

[in] Number of CONNECTDATAstructures returned in rgpcd.

rgpcd

[out] Array to receive enumerated CONNECTDATAstructures.

pcFetched

[out] Pointer to actual number of CONNECTDATAstructures.

Return Value

S_OK if the number of elements supplied is cConnections; S_FALSE otherwise.

Remarks

E_NOTIMPL is not allowed as a return value.

If an error value is returned, no entries in the rgpcdarray are valid on exit and require no release.

To determine whether the platform supports this interface, see Determining Supported COM APIs.

Requirements

Header ocidl.h, ocidl.idl
Library ole32.lib, uuid.lib
Windows Embedded CE Windows CE 3.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.