WD: Problems with AutoExec Macro That Calls Macro in Add-in

Last reviewed: February 18, 1998
Article ID: Q167231
The information in this article applies to:
  • Microsoft Word for Windows, versions 6.0, 6.0a, 6.0c
  • Microsoft Word for Windows 95, versions 7.0, 7.0a
  • Microsoft Word for Windows NT, version 6.0

SYMPTOMS

If you have an AutoExec macro designed to work with an add-in program, Word will return an error based on the task the AutoExec macro is attempting to complete. For example, attempting to call a macro stored in an add-in template results in the following error:

   WordBasic Err=124: Unknown Command, Subroutine, or Function.

CAUSE

By design, WordBasic is asynchronous in operation. This means that while one command is processing, dependent upon the command called, your macro will begin processing the next command.

For example, if your macro processes a command to print a document, and the following command line displays a message box, the message box will appear before the document has completed printing. In Word an AutoExec macro is run before any add-ins are loaded; therefore, the call to the macro stored in your add-in fails and an error occurs.

WORKAROUND

Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web:

     
   http://www.microsoft.com/support/supportnet/refguide/default.asp

The following example macro commands provide a means for working around this limitation by using the OnTime method to delay processing of a macro stored in a template add-in.

The When argument specifies the time at which a macro is to be run. It can be a string that specifies a time (for example, "4:30 pm" or "16:30"), or it can be a serial number returned by a function such as TimeValue or TimeSerial [for example, TimeValue("2:30 pm") or TimeSerial(14, 30, 00)]. You can also include the date [for example, "6/30 4:15 pm" or TimeValue("6/30 4:15 pm")].

Use the sum of the return values of the Now function and either the TimeValue or TimeSerial function to set a timer to run a macro a specified amount of time after the statement is run. For example, use Now+TimeValue("00:05:30") to run a macro 5 minutes and 30 seconds after the statement is run.

The Tolerance argument specifies the maximum time (in seconds) that can elapse before a macro that wasn't run at the time specified by When is canceled. Macros may not always run at the specified time. For example, if a sort operation is under way or a dialog box is being displayed, the macro will be delayed until Word has completed the task. If this argument is 0 (zero) or omitted, the macro is run regardless of how much time has elapsed since the time specified by When.

NOTE: The time to wait will vary between faster and slower computers and may need to be adjusted appropriately.

   OnTime Now() + TimeValue("00:00:3"), "MyMacro", 2


Additional query words:
Keywords : kbmacroexample winword word6 word7 word95 word kbcode kbprg
Version : WINDOWS:6.0,6.0a,6.0c,7.0,7.0a
Platform : NT WINDOWS
Issue type : kbhowto


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 18, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.