Not much w/o trying :) But sometimes Excel behaves weird if somehow references are cyclic.Maybe it doesn't know how to copy itself after itself :)
Cetin

>Cetin,
>
>Besides the solution with null.
>I reviewed my archive more carefully, and discovered this:
>
>*copy the entire sheet(1) After sheet(1)
>oleapp.Sheets(1).Copy(,oleapp.Sheets(1) && does not work !?
>lo=oleapp.Sheets(1)
>lo.Copy(,oleapp.Sheets(1)) && works !?!
>
>Do you have any explanation?
>
>
>>Yuri,
>>Try passing .null. as before parameter
>>Cetin
>>
>>>expression.Move(Before, After)
>>>
>>>For unknown reason I was never able to use "after:" for Move, only "before:". It accepts only one parameter and treats it as "before:".
>>>
>>>>Hello,
>>>>
>>>>I'm trying to automate the creation of a workbook by inserting specific sheets from different workbooks. There is a problem in the syntax of my move which I can't seem to pinpoint.
>>>>
>>>>
>>>>My code:
>>>>myExcel.Application.Workbooks(2).Sheets(1).Move ;
>>>> After:=myExcel.Application.Workbooks(1).Sheets(1)
>>>>
>>>>Thanks in advance!