Ordinal is not valid
Updated: July 20, 2015
For the latest documentation on Visual Studio 2017 RC, see Visual Studio 2017 RC Documentation.
Your call to a dynamic-link library (DLL) indicated to use a number instead of a procedure name, using the
#num syntax. This error has the following possible causes:
An attempt to convert the
#numexpression to an ordinal failed.
#numspecified does not specify any function in the DLL.
A type library has an invalid declaration resulting in internal use of an invalid ordinal number.
Make sure the expression represents a valid number, or call the procedure by name.
#numidentifies a valid function in the DLL.
Isolate the procedure call causing the problem by commenting out the code. Write a
Declarestatement for the procedure, and report the problem to the type library vendor.