Skip to content

Latest commit

 

History

History
87 lines (65 loc) · 2.52 KB

nf-winldap-ldap_first_entry.md

File metadata and controls

87 lines (65 loc) · 2.52 KB
UID title description helpviewer_keywords old-location tech.root ms.assetid ms.date ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames req.redist ms.custom f1_keywords dev_langs topic_type api_type api_location api_name
NF:winldap.ldap_first_entry
ldap_first_entry function (winldap.h)
The ldap_first_entry function returns the first entry of a message.
_ldap_ldap_first_entry
ldap.ldap__first__entry
ldap.ldap_first_entry
ldap_first_entry
ldap_first_entry function [LDAP]
winldap/ldap_first_entry
ldap\ldap_first_entry.htm
ldap
1692d091-7963-492d-9998-5680a2a81088
12/05/2018
_ldap_ldap_first_entry, ldap.ldap__first__entry, ldap.ldap_first_entry, ldap_first_entry, ldap_first_entry function [LDAP], winldap/ldap_first_entry
winldap.h
Windows
Windows Vista
Windows Server 2008
Wldap32.lib
Wldap32.dll
Windows
19H1
ldap_first_entry
winldap/ldap_first_entry
c++
APIRef
kbSyntax
DllExport
Wldap32.dll
ldap_first_entry

ldap_first_entry function

-description

The ldap_first_entry function returns the first entry of a message.

-parameters

-param ld [in]

The session handle.

-param res [in]

The search result, as obtained by a call to one of the synchronous search routines or ldap_result.

-returns

If the search returned valid results, this function returns a pointer to the first result entry. If no entry or reference exists in the result set, it returns NULL. This is the only error return; the session error parameter in the LDAP data structure is cleared to 0 in either case.

-remarks

Use ldap_first_entry in conjunction with ldap_next_entry to step through and retrieve the list of entries from a search result chain.

You do not have to explicitly free the returned entry as it is freed when the message itself is freed.

-see-also

Functions

ldap_next_entry

ldap_result