Yes, that will refuse DDE requests, like those from Explorer etc., so WBs
will open in another instance of Excel.
Your instance is not immune from interaction with COM, but someone/some app
would (normally) have to go looking for your instance, although GetObject
could return it.

NickHK

"Huey" wrote in message
...
I found that others have been able to do what I want by using this :

Application.IgnoreRemoteRequests = True

This will stop any new workbooks from opening in the Application object
referred to in the above code.

I thank you. ;]

"Huey" wrote:

That's what I want to know. All I do is double-click on a spreadsheet
either
from a file browser or as an attachement from an email and it pops up in
the
application object that my script created.

I did find that there is an Application.Interactive property I could set
to
False but the Help information reads like this only disables input from
the
user and so I might just hose myself if I set this to False in my
script.
I'm at home now so I can't easily try this on my script so I'll check
back in
tomorrow.

"Norman Jones" wrote:

Hi Huey,

'-----------------
Norman, It is hidden to begin with. But it becomes visible when I
manually
open a different workbook. What I am hoping for is some setting in
the
Excel
application object that will make it "private" so that no other
processes
can
interact with it.
'-----------------

How did you open a workbook manually in a hidden
instance of Excel?


---
Regards,
Norman