Does the execution jump from one procedure in one application to a different
procedure in another application? This statement makes me cringe: "the
calling Access file has been closed". I think I'd be a little leery of
switching the execution like this. Couldn't you add the proper application
and object references to the Excel based code and port it into the Access
project? This would keep execution in one context only, although it could do
all the same stuff as if it switched around.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
http://PeltierTech.com
_______


"BAC" wrote in message
...
I posted this several days ago but still have not gotten any replies. I've
tried everything I can think of, but can't find a solution...


Xp pro, Office 2003 Pro

I have a routine that begins in Access, moves to Excel, then returns
results
from Excel back to Access.

In the middle of the Excel portion of the VBA (the calling Access file has
been closed) the VBA begins and continues to arbitrarily spit out a "Code
execution has been interrupted" dialog box. Selecting Debug turns up a
different code line each time; selecting continue allows the routine to
continue until the next "arbitrary" interruption.

This did not occure when we were running Win 2000 Pro and Office 2000 Pro.
Is this an XP or Office 2003 issue?

I have "googled" the error and found several discussions of this activity,
but have yet to find a clear delineation of its cause or a clear
process/procedure for eliminating it, even tho some real heavy hitters
(MVP's) have addressed this question. Even the KB is really weak in this
area.

Any help would be appreciated - my users are looking for my head!

BAC