ACC97: "Convert Macros to Visual Basic" Converts Incorrectly

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q167061

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

SYMPTOMS

When you run the "Convert Macros to Visual Basic" command on a macro that has any of the following RunCommand actions

   RunCommand ArrangeIconsByCreated
   RunCommand ArrangeIconsByModified
   RunCommand ArrangeIconsByName
   RunCommand ArrangeIconsByType
   RunCommand StepInto
   RunCommand FindNext
   RunCommand HyperlinkDisplayText

the macro actions are converted to the following methods of the DoCmd object in the module

   DoCmd.RunCommand acCmdSortByCreated    (ArrangeIconsByCreated)
   DoCmd.RunCommand acCmdSortByModified   (ArrangeIconsByModified)
   DoCmd.RunCommand acCmdSortByName       (ArrangeIconsByName)
   DoCmd.RunCommand acCmdSortByType       (ArrangeIconsByType)
   DoCmd.RunCommand <blank>               (StepInto)
   DoCmd.RunCommand <blank>               (FindNext)
   DoCmd.RunCommand acCmdEnterEditMode    (HyperlinkDisplayText)

and you receive the following compile error when you try to compile the module:

Compile error

Variable not defined.

Back to the top

CAUSE

The "Convert Macros to Visual Basic" command on the Macro submenu, incorrectly converts the macro actions.

Back to the top

RESOLUTION

You must manually change the syntax for the RunCommand actions in the module.

Back to the top

MORE INFORMATION

The following table lists the correct syntax for the converted macro actions.

Converted Syntax                    Correct Syntax
--------------------------------------------------

RunCommand ArrangeIconsByCreated    DoCmd.RunCommand acCmdArrangeIconsBy
                                    Created.

RunCommand ArrangeIconsByModified   DoCmd.RunCommand acCmdArrangeIconsBy
                                    Modified.

RunCommand ArrangeIconsByName       DoCmd.RunCommand acCmdArrangeIconsBy
                                    Name.

RunCommand ArrangeIconsByType       DoCmd.RunCommand acCmdArrangeIconsBy
                                    Type.

RunCommand StepInto                 DoCmd.RunCommand acCmdStepInto.

RunCommand FindNext                 DoCmd.RunCommand acCmdFindNext.

RunCommand HyperlinkDisplayText     DoCmd.RunCommand acCmdHyperlinkDisplay
                                    Text.

Back to the top

Steps to Reproduce Behavior

Open a new database in Microsoft Access 97.

Create a new macro and add the following actions to the macro:

      Macro Name           Macro Action
      ---------------------------------
      Macro1               RunCommand
                           RunCommand
                           RunCommand
                           RunCommand
                           RunCommand
                           RunCommand
                           RunCommand

      Macro1 Actions
      ----------------------------------
      RunCommand
         Command: ArrangeIconsByCreated
      RunCommand
         Command: ArrangeIconsByModified
      RunCommand
         Command: ArrangeIconsByName
      RunCommand
         Command: ArrangeIconsByType
      RunCommand
         Command: StepInto
      RunCommand
         Command: FindNext
      RunCommand
         Command: HyperlinkDisplayText

Save the macro as Macro1 and close it.
Select Macro1 in the Database window, and then on the Tools menu, point to Macro, and click "Convert Macros to Visual Basic."
After the module has been created, open it in Design view, and then on the Debug menu, click Compile Loaded Modules. Note that you receive the compile error 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

kberrmsg kbprb KB167061

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top