Error Codes

The LEADTOOLS toolkit returns error and success notifications to applications in the form of HRESULT values.

A return code's LOWORD portion is the return code itself, in hexadecimal format.

The COM Win32 HRESULT documentation contains more information, including how to use the FAILED and SUCCEEDED macros to test return values.

Microsoft Visual Basic® programmers will see only the decimal equivalent of the error code's first 16-bit portion. This value appears in an error notification dialog box or in the Err object as a run-time error. If the error is not in the following list, you must convert the decimal number to its hexadecimal equivalent, and then look for the error as described previously. Note that the error's hexadecimal version will be a maximum of four digits long; to find the error, match the last four digits of the hexadecimal code in the error code list to the converted run-time error.

The LEADTOOLS filters will return E_EVAL_EXPIRED (0x80050010) if you attempt to create them after the evaluation period has expired.

Some components will convert DOS error codes to 0x8003zzzz, where "zzzz" is the error code. For example, the DOS error code ERROR_PATH_NOT_FOUND (0x03) is converted to 0x80030003. For a complete list, see the GetLastError function in the Microsoft Platform SDK documentation.