XEQ stops spontaneously

  • Thread starter Thread starter Fred Rosenberg
  • Start date Start date
F

Fred Rosenberg

hi,

one of my clients has an application written in Access 2000, it's about 8MB
in size. It is a mini-datawarehouse application, and chugs thru lots of
data. every now and then, it just stops at a line of code in a procedure,
as if there was a breakpoint there. but there is not. pressing F5
(continue), and it continues executing on its merry way.

this is a hassle, since often it runs during the night, and no one is around
to start it going again!

any clues to what this might be and how to fix it?

thanks!

fred
 
Fred Rosenberg said:
hi,

one of my clients has an application written in Access 2000, it's
about 8MB in size. It is a mini-datawarehouse application, and chugs
thru lots of data. every now and then, it just stops at a line of
code in a procedure, as if there was a breakpoint there. but there
is not. pressing F5 (continue), and it continues executing on its
merry way.

this is a hassle, since often it runs during the night, and no one is
around to start it going again!

any clues to what this might be and how to fix it?
Click to expand...

I've only seen this when there had previously been a breakpoint set at
that line -- somehow a "phantom" breakpoint has been left behind. I
don't know if this is what has been happening in your case or not. What
I've usually done to get rid of it is open up a code module, modify a
line slightly and then change it back (to mark the project as dirty),
click Debug -> Clear All Breakpoints, then click Debug -> Compile, and
finally click Save.

If that fails, you might try (on a *copy* of the application!)
decompiling the project using the /decompile command-line switch. After
decompiling, compact the database, then compile it, then compact again.
If the copy you did this with seems to be working fine, then swap it in
for the original, saving the original in case of trouble.
 
thanks dick, i'll give it a try!

fred


Dirk Goldgar said:
I've only seen this when there had previously been a breakpoint set at
that line -- somehow a "phantom" breakpoint has been left behind. I
don't know if this is what has been happening in your case or not. What
I've usually done to get rid of it is open up a code module, modify a
line slightly and then change it back (to mark the project as dirty),
click Debug -> Clear All Breakpoints, then click Debug -> Compile, and
finally click Save.

If that fails, you might try (on a *copy* of the application!)
decompiling the project using the /decompile command-line switch. After
decompiling, compact the database, then compile it, then compact again.
If the copy you did this with seems to be working fine, then swap it in
for the original, saving the original in case of trouble.

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)
Click to expand...
 
Back
Top