XL2000: No "Record at Mark" Feature in Microsoft Excel

You cannot record a Microsoft Visual Basic for Applications (VBA) macro within another macro in Microsoft Excel. This feature is available in versions of Microsoft Excel earlier than Excel 97.

Because of the major changes made to the Visual Basic for Applications environment in Microsoft Excel 97, this functionality is no longer available.

To work around this problem, use either of the following methods.

Use the 'Record at Mark 2000 for Excel 2000' Add-In

You can download an Excel 2000 add-in that replicates the "Record at Mark" feature. This allows you to record your code directly into an existing Visual Basic for Applications procedure at the location that you specify.

To download this add-in, please see the following Microsoft Web page: For more information about the support of this add-in, please see the support information at the bottom of the above Web page.

The add-in that is discussed in this article is provided as-is. Microsoft does not guarantee that it can be used in all situations. Although Microsoft Support Professionals can help with the installation and existing functionality of this add-in, they will not modify the add-in to provide new functionality.

Paste Newly Recorded Code into an Existing Procedure

If you want to record a Visual Basic for Applications macro within another macro, follow these steps:

1. Record your macro.
2. Start the Visual Basic Editor by pressing ALT+F11.
3. Select the code in your newly recorded macro; copy it, and paste it into your existing macro.

The following menu items are available in versions of Microsoft Excel earlier than Excel 97. In versions of Microsoft Excel earlier than Excel 97, you can use these menu items to record a Visual Basic for Applications macro within another macro.

These menu items, and the functionality they provide, are not available in Microsoft Excel 97 or later. To circumvent this limitation, use the steps shown in the "Workaround" section of this article.

For additional information about this behavior in earlier versions of Microsoft Excel, click the article number below to view the article in the Microsoft Knowledge Base: