XL5 Err Msg: "That Name Is not Valid" with Macro Translator

• Microsoft Excel for Windows, version 5.0

SYMPTOMS

In Microsoft Excel version 5.0, when you use the Macro Translation Assistant (MTA) to translate a Lotus 1-2-3 macro, you may receive one or both of the following error messages:

That name is not valid

Translation Error: Can't Communicate with Microsoft Excel

CAUSE

This error message appears when the Macro Translation Assistant, which is included with Microsoft Excel version 5.0, attempts to translate a Lotus 1-2-3 macro that has a name beginning with a backslash (\) or forward slash (/). The Macro Translation Assistant attempts to create a \ or / name on a macro sheet when it translates a Lotus 1-2-3 macro. Microsoft Excel version 5.0 global naming conventions do not permit the creation of a name that is preceded by a backslash (\) or forward slash (/).

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

NOTE: The Macro Translation Assistant is not included with Microsoft Excel versions 5.0c and later.

WORKAROUND

To work around this problem, do the following to rename all of the Lotus 1-2-3 macros so that the macro names do not contain backslashes (\):

1. Open the Lotus 1-2-3 (.WK*) file that contains the Lotus 1-2-3 macros.



2. From the Insert menu, choose Name, and then choose Define.



3. Select the Lotus 1-2-3 macro names that contain the backslashes, (the name will be followed by a letter, such as \a).



4. Change the name to one without a backslash (\) preceding the letter. After you change the name, choose Add, and then choose OK to accept the changes.

REFERENCES

For information on running a Lotus 1-2-3 macro in Microsoft Excel, choose the Search button in Help and type:

   Lotus macro conversion running 

Additional query words: 123 slash backslash

Keywords :
Version : 5.00
Platform : WINDOWS
Issue type :