Visual Basic for Applications Reference

  • Article

Invalid ordinal (Error 452)

Specifics

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 causes and solutions:

  • An attempt to convert the num expression to an ordinal failed.

    Make sure the expression represents a valid number or call the procedure by name.

  • The num specified doesn't specify any function in the DLL.

    Make sure num identifies a valid function in the DLL.

  • A type library has an invalid declaration resulting in internal use of an invalid ordinal number.

    comment out code to isolate the procedure call causing the problem. Write a Declare statement for the procedure and report the problem to the type library vendor.

For additional information, select the item in question and press F1.