ACC97: RunCommand Constants Truncated After 25 Characters

ID: Q168311

The information in this article applies to:

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

When you convert any of the following RunCommand macro actions 


   RunCommand CompileAndSaveAllModules
   RunCommand ConvertMacrosToVisualBasic
   RunCommand CreateShortcutMenuFromMacro
   RunCommand HorizontalSpacingMakeEqual
   RunCommand MicrosoftAccessHelpTopics
   RunCommand ObjBrwFindWholeWordOnly
   RunCommand ObjBrwShowHiddenMembers
   RunCommand QueryTypeSQLDataDefinition
   RunCommand QueryTypeSQLPassThrough
   RunCommand UserLevelSecurityWizard
   RunCommand VerticalSpacingMakeEqual

using the "Convert Macro to Visual Basic" command, the syntax is truncated during the conversion, and you receive the following error message when you compile the converted macro module:
Compile error:

Variable not defined


CAUSE

There is a 25 character limitation for the RunCommand constants when using the "Convert Macro to Visual Basic" command. This includes the acCmd prefix that is attached to the constant during the conversion.


RESOLUTION

To prevent your code from failing with a compile error, modify the syntax for the truncated constants before you compile and run the module.


MORE INFORMATION

Steps to Reproduce Behavior


  1. Create a new database in Microsoft Access 97.


  2. Create a new macro, and add the following RunCommand actions to the macro: 
    
      Macro Name           Macro Action
      ---------------------------------
      Macro1               RunCommand
                           RunCommand
                           RunCommand

      Macro1 Actions
      --------------------------------------
      RunCommand
         Command: CompileAndSaveAllModules
      RunCommand
         Command: ConvertMacrosToVisualBasic
      RunCommand
         Command: UserLevelSecurityWizard


  3. Save the macro as Macro1.


  4. Select Macro1 in the Database window. On the Tools menu, point to Macro, and then click "Convert Macro to Visual Basic."


  5. After the conversion process is finished, open the converted macro module. Note the truncated constants.


  6. On the Debug menu, click Compile Loaded Modules. Note that you receive the error message mentioned in the "Symptoms" section.



REFERENCES

For more information about converting macros, search the Help Index for "macros, converting," and then "convert macros to Visual Basic," or ask the Microsoft Access 97 Office Assistant. 


Keywords          : kbcode kberrmsg McrActn 
Version           : 97
Platform          : WINDOWS 
Issue type        : kbprb

Last Reviewed: April 30, 1999