>>Posted code ? If to email I haven't checked my emails today yet :) I'll. If else more info pls.
>>
>>Cetin,
>>
>>Thread#308023 is the start. Message#308893 is the class code. Many thanks.
>
>

---

I have additional thoughts for the class code ( my God, you're extra OOP :) for later (such as a selection itself is a range object and you could just say :
>...selection.value = 0, .selection.clear etc).
>
>But for the Excel task. Instead of checking window via WinAPI try checking files RW openability (been there done that:)
>
>

lnHandle = fopen(pcFile,12)
>do while lnHandle < 0
> lnHandle = fopen(pcFile,12)
>enddo
>* Now release oExcel

If you get the window way, take window id of worksheet not Excel itself (and I bet you do it much better than I).
>And check your email frequently :)
>Cetin

Will do, Cetin, and thanks.

There are a couple of reasons that the code is written the way it is. First, I only hope that I'll end up using Excel. I'm still trying to do this with Lotus 1-2-3 (after far too many hours). I wanted to design the application so that all the necessary actions were internalized by the class. Whatever calls the class simply needs to be aware of the interface rather than the implementation. For example, to minimize or maximize (necessary steps, BTW) the application, you (as you know) set the .WindowState property in Excel. In 1-2-3 you call the .Maximize or .Minimize methods.

Another point was that Excel 2000 spawns additional instances of itself everytime an additional sheet/workbook is opened. In fact, it makes me wonder if using GETOBJECT() even should be considered.

I will take a look at your suggestions, however, and do appreicate your input. I've reported the problem to MS, but maybe your suggestion will provide a workaround.