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

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

The changing versions brings another thought to mind. Are there any missing
references in the 2003 version of the program? These often manifest
themselves in seemingly unrelated ways, with perfectly valid statements
causing errors.

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


"Jon Peltier" wrote in message
...
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

Jon: My macros have done the same thing, and they are all contained with
Excel. My Word macros have done it, too. Most of the time it's only on one
computer. It's a very arbitrary stopping point - never the same place.
Pressing F5 or clicking Continue makes the code move on as if nothing
happened. There are no break points, no errors, no missing objects. Just a
random stop like an old car I used to have. 8( This is with both
Office 2000 and XP under both Win 2000 and XP.

Ed

"Jon Peltier" wrote in message
...
The changing versions brings another thought to mind. Are there any
missing references in the 2003 version of the program? These often
manifest themselves in seemingly unrelated ways, with perfectly valid
statements causing errors.

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


"Jon Peltier" wrote in message
...
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

Hi All,

I have experienced similar problems in the past, especially when
running code (Which l know to be OK) on different PC's, operating
systems etc.

This may seen simplistic but l ahve found it is often caused by a
'sticky' Esc or Break key.

Hope this helps,

Regards

Michael Beckinsale

This can happen when VBA's internal code storage area get screwed up. The
best solution is to Export all code to text files, delete all modules and
all code, then Import the text files. This will cause VBA to purge all its
internal code storage areas and start with a clean slate. Rob Bovey has a
excellent add-in that automates this whole process down to two or three
mouse clicks.

See http://www.appspro.com/Utilities/CodeCleaner.htm

Rob's Code Cleaner is a "must have" add-in for any serious Excel
development.

--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting, LLC
www.cpearson.com
(email address is on the web site)



"michael.beckinsale" wrote:

Hi All,

I have experienced similar problems in the past, especially when
running code (Which l know to be OK) on different PC's, operating
systems etc.

This may seen simplistic but l ahve found it is often caused by a
'sticky' Esc or Break key.

Hope this helps,

Regards

Michael Beckinsale

Well, then, seems I'm not alone!


"Ed" wrote:

Jon: My macros have done the same thing, and they are all contained with
Excel. My Word macros have done it, too. Most of the time it's only on one
computer. It's a very arbitrary stopping point - never the same place.
Pressing F5 or clicking Continue makes the code move on as if nothing
happened. There are no break points, no errors, no missing objects. Just a
random stop like an old car I used to have. 8( This is with both
Office 2000 and XP under both Win 2000 and XP.

Ed

"Jon Peltier" wrote in message
...
The changing versions brings another thought to mind. Are there any
missing references in the 2003 version of the program? These often
manifest themselves in seemingly unrelated ways, with perfectly valid
statements causing errors.

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


"Jon Peltier" wrote in message
...
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

Not at all - in having the problem and in lacking an answer!
Ed

"BAC" wrote in message
...
Well, then, seems I'm not alone!


"Ed" wrote:

Jon: My macros have done the same thing, and they are all contained with
Excel. My Word macros have done it, too. Most of the time it's only on
one
computer. It's a very arbitrary stopping point - never the same place.
Pressing F5 or clicking Continue makes the code move on as if nothing
happened. There are no break points, no errors, no missing objects.
Just a
random stop like an old car I used to have. 8( This is with both
Office 2000 and XP under both Win 2000 and XP.

Ed

"Jon Peltier" wrote in message
...
The changing versions brings another thought to mind. Are there any
missing references in the 2003 version of the program? These often
manifest themselves in seemingly unrelated ways, with perfectly valid
statements causing errors.

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


"Jon Peltier" wrote in message
...
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

This can happen when VBA's internal code storage area get screwed up. The
best solution is to Export all code to text files, delete all modules and
all code, then Import the text files. This will cause VBA to purge all its
internal code storage areas and start with a clean slate. Rob Bovey has a
excellent add-in that automates this whole process down to two or three
mouse clicks.

See http://www.appspro.com/Utilities/CodeCleaner.htm

Rob's Code Cleaner is a "must have" add-in for any serious Excel
development.

--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting, LLC
www.cpearson.com
(email address is on the web site)



"Ed" wrote:

Jon: My macros have done the same thing, and they are all contained with
Excel. My Word macros have done it, too. Most of the time it's only on one
computer. It's a very arbitrary stopping point - never the same place.
Pressing F5 or clicking Continue makes the code move on as if nothing
happened. There are no break points, no errors, no missing objects. Just a
random stop like an old car I used to have. 8( This is with both
Office 2000 and XP under both Win 2000 and XP.

Ed

"Jon Peltier" wrote in message
...
The changing versions brings another thought to mind. Are there any
missing references in the 2003 version of the program? These often
manifest themselves in seemingly unrelated ways, with perfectly valid
statements causing errors.

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


"Jon Peltier" wrote in message
...
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

On Feb 27, 5:03 am, BAC wrote:
This can happen when VBA's internalcodestorage area get screwed up. The
best solution is to Export allcodeto text files, delete all modules and
allcode, then Import the text files. This will cause VBA to purge all its
internalcodestorage areas and start with a clean slate. Rob Boveyhasa
excellent add-in that automates this whole process down to two or three
mouse clicks.

Seehttp://www.appspro.com/Utilities/CodeCleaner.htm

Rob'sCodeCleaner is a "must have" add-in for any seriousExcel
development.

--
Cordially,
Chip Pearson
Microsoft MVP -Excel
Pearson Software Consulting, LLCwww.cpearson.com
(email address is on the web site)



"Ed" wrote:
Jon: My macros have done the same thing, and they are all contained with
Excel. My Word macros have done it, too. Most of the time it's only on one
computer. It's a very arbitrary stopping point - never the same place.
Pressing F5 or clicking Continue makes thecodemove on as if nothing
happened. There are no break points, no errors, no missing objects. Just a
random stop like an old car I used to have. 8( This is with both
Office 2000 and XP under both Win 2000 and XP.

Ed

"Jon Peltier" wrote in message
...
The changing versions brings another thought to mind. Are there any
missing references in the 2003 version of the program? These often
manifest themselves in seemingly unrelated ways, with perfectly valid
statements causing errors.

- Jon
-------
Jon Peltier, MicrosoftExcelMVP
Tutorials and Custom Solutions
http://PeltierTech.com
_______

"Jon Peltier" wrote in message
...
Does theexecutionjump from one procedure in one application to a
different procedure in another application? This statement makes me
cringe: "the calling Access filehasbeenclosed". I think I'd be a
little leery of switching theexecutionlike this. Couldn't you add the
proper application and object references to theExcelbasedcodeand port
it into the Access project? This would keepexecutionin one context
only, although it could do all the same stuff as if it switched around.

- Jon
-------
Jon Peltier, MicrosoftExcelMVP
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 toExcel, then returns
results
fromExcelback to Access.

In the middle of theExcelportion of the VBA (the calling Access file
has
beenclosed) the VBA begins and continues to arbitrarily spit out a
"Code
executionhasbeeninterrupted" dialog box. Selecting Debug turns up a
differentcodeline 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- Hide quoted text -

- Show quoted text -

Hi,

Mine now stops randomly within the code of the Code Cleaner!!

Can anyone beat that??

I've vrified all the required references. The Excel portion of the routine is
an automation of a 28 step process that was done a couple years ago, and to
be honest with you, it's a bit convoluted so i really don't want to mess with
it.

It worked fine under Win 2000/Office 2000

"Jon Peltier" wrote:

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

Hi, try posting the code snippet to get help faster.

"BAC" wrote:

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

The code is like "pages" long and, like I said the stop is pretty much
arbitrary.across procedures and functions


"Madhan" wrote:

Hi, try posting the code snippet to get help faster.

"BAC" wrote:

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