Help and Support
 

powered byLive Search

ACC97: RunCommand Constants Truncated After 25 Characters

View products that this article applies to.
Article ID:168311
Last Review:January 19, 2007
Revision:3.1
This article was previously published under Q168311
Moderate: Requires basic macro, coding, and interoperability skills.

On This Page

SYMPTOMS

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

Back to the top

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.

Back to the top

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.

Back to the top

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.

Back to the top

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.

Back to the top

APPLIES TO
•Microsoft Access 97 Standard Edition

Back to the top

Keywords: 
kbcode kberrmsg kbprb KB168311

Back to the top

Article Translations

 

Other Support Options

  • Need More Help?
    Contact a Support professional by Email, Online or Phone.
  • Customer Service
    For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
  • Newsgroups
    Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.