EXPORT_CALLBACK

The EXPORT_CALLBACK structure contains information about a function that is invoked on export callback.

Quick Info

typedef struct
{
  DWORD                dwFlags;
  DAPI_EVAL            ulEvalTag;
  LPVOID               lpvAppDefined;
  PDAPI_FNExportEntry  pfnExportEntry;
}  EXPORT_CALLBACK, * PEXPORT_CALLBACK;

Members

dwFlags

Reserved (set to zero).

ulEvalTag

The type of data pointed to by lpvAppDefined:

TEXT_LINE

The data items are delimited by commas or other specified characters. The data line format is the same as if the data were written to an export file.

TEXT_VALUE_ARRAY

The items are in an array of structures where binary and nonbinary data is represented as strings. Binary values are exported as strings of hexadecimal digits.

VALUE_ARRAY

The items are in their native type, with a few minor exceptions. For example, any attributes whose native type is object (such as distinguished names or OR names) are represented as text. Also, date fields are represented as UTC strings of the date. Unsigned integer values are represented as integers.

lpvAppDefined

Application-defined field, passed as a parameter to the callback.

pfnExportEntry

Points to a function that processes each exported entry. For additional information, see the DAPI_FNExportEntry function prototype.

Remarks

Information in the EXPORT_CALLBACK structure is used to control the export of data with a callback function. Its members specify, for example, the name of the callback function itself and the format in which data is to be exported. A function specified in the EXPORT_CALLBACK structure is called each time an object is exported by the BatchExport, NTExport, and NWExport functions.

For additional information on this structure, see Importing and Exporting with Directory Access Functions.

See Also

BEXPORT_PARMS, DAPI_FNErrorCallback, DAPI_FNExportEntry, NTEXPORT_PARMS, NWEXPORT_PARMS