NWGetObjectID

Looks up an object ID in the bindery on the network server associated with the given connection handle

Local Servers:blocking
Remote Servers:blocking
NetWare Server:3.11, 3.12, 4.x, 5.x, 6.x
Platform:NLM, Windows NT, Windows 95, Windows 98
Library:Cross-Platform NetWare Calls (CAL*.*)
Service:Bindery

Syntax

C

   #include <nwbindry.h> 
   or 
   #include <nwcalls.h> 
    
   NWCCODE N_API  NWGetObjectID  ( 
      NWCONN_HANDLE       conn,  
      const nstr8 N_FAR  *objName,  
      nuint16             objType,  
      pnuint32            objID);
   

Pascal

   uses calwin32 
    
   Function NWGetObjectID 
     (conn : NWCONN_HANDLE; 
      const objName : pnstr8; 
      objType : nuint16; 
      objID : pnuint32 
   ) : NWCCODE; stdcall;
   

Parameters

conn
(IN) Specifies the NetWare server connection handle.
objName
(IN) Points to the name of the object in the search.
objType
(IN) Specifies the type of the object in the search.
objID
(OUT) Points to the ID of the found object.

Return Values

These are common return values. See Return Values (Return Values for C).

0x0000

SUCCESSFUL

0x8801

INVALID_CONNECTION

0x890A

NLM_INVALID_CONNECTION

0x8996

SERVER_OUT_OF_MEMORY

0x89F0

WILD_CARD_NOT_ALLOWED

0x89F1

INVALID_BINDERY_SECURITY

0x89FC

NO_SUCH_OBJECT

0x89FE

BINDERY_LOCKED

0x89FF

HARDWARE_FAILURE

Remarks

Since each network server contains its own bindery, object IDs are not consistent across network servers.

The objName and objType parameters must uniquely identify the bindery object and cannot contain wildcard characters.

The requesting process must be logged in to the network server and have Read access to the bindery object for NWGetObjectID to be successful.

NWGetObjectID can be called even if a connection is not authenticated.

See Object Type.

NCP Calls

See Also

NWChangeObjectSecurity, NWCreateObject