Just found another link that may help on this topic...

http://www.ureader.com/message/692318.aspx

Mark

"Steve C" wrote in message
...
I discovered something interesting by accident today. With Excel closed,
I
run the export from ACT! and get the error, as usual. But if I open
another
Excel file in Windows Explorer (not through File Open in Excel, but
rather
by double-clicking an existing file), not only does that file open, but my
export from ACT! opens with it! Very strange. This does not happen if I
open Excel by itself or if I open that same Explorer file from within
Excel.

It's as if the export from ACT is initially being "hidden" from view and
doesn't get triggered until I open another Excel file via Explorer. The
export appears to stay in "memory" in Excel for as long as I'm logged on.
In
investigating this error, I've read how some programs open a separate
instance of Excel to display the data, and perhaps that is happening here.
Now that I know this is happening, I can at least do this "work-around" to
see my data, but it sure is odd!
--
Steve C


"Mark Ivey" wrote:

You might want to see if there is any instance of Excel already running
before your code gets to this part and issue a prompt for the user to
close
it down before proceeding Would this suffice?

Mark

"Steve C" wrote in message
...
Mark,

Thank you for your response. After trying the settings suggested, I'm
still
getting the same error. From what I've been reading on this topic, it
may
be
related to ACT! trying to open a separate instance of the Excel
application.
Do you know of any means to cause this not to happen when Excel is
launched
by ACT!?


-- Steve C


"Mark Ivey" wrote:

See if this helps...

http://support.microsoft.com/kb/282830/

Programmatic access to Office VBA project is denied

SYMPTOMS
Code that is written to automate an Office application and
programmatically
manipulate the Microsoft Visual Basic for Applications (VBA)
environment
and
object model may fail on Office with one of the following error
messages:

From Visual Basic or VBA:
HRESULT = 0x800A17B4 (-2146822220) "Programmatic Access to Visual
Basic
Project is not trusted"
The same code works without error on computers with Office 97 and
Office
2000.


Mark Ivey