XL: Error Using XLCALL and SaveAs Functions

ID: Q126094

The information in this article applies to:

SYMPTOMS

In Microsoft Excel, you may receive a macro error when you use the XLCALL function in a Lotus 1-2-3 macro to call a Microsoft Excel Visual Basic for Applications module that contains the SaveAs function.

CAUSE

You receive an error at the cell that contains the XLCALL function if the Microsoft Excel macro that is called contains a SaveAs command, and either of the following conditions occurs:

The Microsoft Excel procedure that is called is run; but when it returns control to the XLCALL function, an error occurs.

WORKAROUND

Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact the Microsoft fee-based consulting line at (800) 936-5200. For more information about the support options available from Microsoft, please see the following page on the World Wide Web: 

   http://www.microsoft.com/support/supportnet/refguide/
To work around this problem, use any of the following methods.

Method 1

If the SaveAs command saves the workbook that contains the XLCALL function under a different name, modify the SaveAs function so that the module saves the workbook containing the XLCALL function under the same name.

Method 2

If the SaveAs command saves another workbook, switch to the workbook and worksheet that contains the {XLCALL} function before it leaves the sub procedure. The following procedure, which is called from Test.xls, opens a new workbook and saves it as Book.xls. It then switches to the worksheet in which the XLCALL command is located (Test.xls). 

   Sub SheetSave()
       'Open new workbook
       Workbooks.Add

       'Save new workbook as Book.xls
       ActiveWorkbook.SaveAs FileName:="Book.xls", FileFormat:=xlNormal

       'Activate Test.xls, which is where the XLCALL
       'command is located
       Workbooks("Test.xls").Activate
       Worksheets("A").Activate
   End Sub

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

MORE INFORMATION

The XLCALL command is used to call a Microsoft Excel macro or module from a Lotus 1-2-3 macro. The syntax for this command is as follows: 

   {XLCALL macro_name}
Where macro_name is the name of the Microsoft Excel macro being called. For example, this will run a Visual Basic for Applications macro called Macro1 located in Module1 of the active workbook. 

   {XLCALL Module1.Macro1}

REFERENCES

"Microsoft Excel User's Guide," version 5.0, Chapter 3, "Microsoft Excel for Windows Runs 1-2-3 Macros"

Additional query words: 5.00 7.00 8.00 97 XL97 XL7 XL5 

Keywords          : kbmacro kbprg kbdta kbdtacode KbVBA 
Version           : WINDOWS:5.0,5.0c,7.0,7.0a,97; MACINTOSH:5.0
Platform          : MACINTOSH WINDOWS
Issue type        : kbbug
Solution Type     : kbpending

Last Reviewed: May 18, 1999