Re: Let's try again: VBA Code stops randomly

On Feb 27, 5:03 am, BAC <B...@xxxxxxxxxxxxxxxxxxxxxxxxx> 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" <jonxlmv...@xxxxxxxxxxxxxxxxxxx> wrote in message
news:%23RbPonbVHHA.4796@xxxxxxxxxxxxxxxxxxxxxxx
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" <jonxlmv...@xxxxxxxxxxxxxxxxxxx> wrote in message
news:eyv3DgbVHHA.4756@xxxxxxxxxxxxxxxxxxxxxxx
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" <B...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1EA44B18-2F6F-4E11-8885-4171A20A3479@xxxxxxxxxxxxxxxx
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??


.

Loading