The macro is in Module1 of the Macros.xls file.

The macro actually runs correctly, it looks like the error occurs in between the macro running and the next line of code where Excel becomes visible. I never see Excel, FoxPro goes straight into my error routine.

>Is the OLE exception error related to the fact that it cannot find the master macro???
>
>Setting visible = .T. has no effect on things...
>
>You need to make sure you macro is in a module....
>
>>I am using Office 2000, the error occurs on the "run" line.
>>
>>I forgot one other line of code that I am running just after the "run" line:
>>
>>oEXCEL.APPLICATION.VISIBLE = .T.
>>
>>I don't know if that will make a difference or not.
>>
>>>I am using VS 6 SP 3 and Office 2000. I created a macros.xls and added a macro called master. Your code ran fine...
>>>
>>>What version of Office are you using? And, does the error occur on a specific line?
>>>
>>>>John,
>>>>
>>>>I keep getting an OLE error when trying to run an Excel macro using OLE Automation. I have searched everywhere for a solution and can't find anything. I was wondering if you've ever tried to run an Excel macro using VFP or VB.
>>>>
>>>>I first tried an Auto_Activate macro. It worked fine if I opened the workbook using Excel, but when I used VFP 5.0 and OLE Automation to open the workbook it would not run the macro. So I renamed the macro to "Master" and tried to run it after the workbook was already open.
>>>>
>>>>The macro actually runs but I get the following message afterward:
>>>> OLE error code Ox800a9c68: Unknown OLE status code
>>>>
>>>>I tried it in VFP 6.0 and got this:
>>>> OLE error code Ox800a9c68: Unknown COM status code
>>>>
>>>>Here is the code I'm using.
>>>>
>>>>oEXCEL = CREATEOBJECT("Excel.Application")
>>>>oEXCEL.Workbooks.Open("MACROS.XLS")
>>>>oEXCEL.Application.Run("'MACROS.XLS'!Master")
>>>>oEXCEL.QUIT()
>>>>RELEASE oEXCEL
>>>>
>>>>I did find a similar confirmed bug ("Unknown COM status code" With ActiveX Conferencing Control) that was corrected in Visual Studio 6.0 Service Pack 3.
>>>>
>>>>Could this just be another bug?
>>>>
>>>>Any help would be appreciated.
>>>>
>>>>Thanks,