B
Brendan on Comcast.net
in my Access 2003 VBA event procedure, the "stop" command no longer stops
execution.
It used to work.
any ideas?
Thank you.
execution.
It used to work.
any ideas?
Thank you.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
A
Allen Browne
In the code window, go to:
Tools | Options | General
and set Error Trapping to:
Break on Unhandled Errors
While you are there, make sure the Compile On Demand is unchecked.
If that does not solve the problem, decompile the database. Make sure the
database is not open, and enter something like this at the command prompt.
It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
Tools | Options | General
and set Error Trapping to:
Break on Unhandled Errors
While you are there, make sure the Compile On Demand is unchecked.
If that does not solve the problem, decompile the database. Make sure the
database is not open, and enter something like this at the command prompt.
It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
B
Brendan on Comcast.net
Hi Allen, thanks for the quick feedback
my database already had the Break on Unhandled Errors selected.
I decompiled as you suggested (...\office11\msaccess.exe"...)
now I get an error ... variable not defined.
So then I selected the "compile on demand" option and I'm back to where I
was, ie "Stop" doesn't.
Any other ideas?
I appreciate all of your help here!
Brendan
my database already had the Break on Unhandled Errors selected.
I decompiled as you suggested (...\office11\msaccess.exe"...)
now I get an error ... variable not defined.
So then I selected the "compile on demand" option and I'm back to where I
was, ie "Stop" doesn't.
Any other ideas?
I appreciate all of your help here!
Brendan
R
RD
Brendan,
Are you certain that the code is executing up to the Stop? You might want to
put a Breakpoint at the begining of the procedure and step through it to check.
A stop won't work if you never get there.
Just a thought,
RD
Are you certain that the code is executing up to the Stop? You might want to
put a Breakpoint at the begining of the procedure and step through it to check.
A stop won't work if you never get there.
Just a thought,
RD
A
Allen Browne
Might be worth checking that you have not disabled Special Keys.
Compile on demand is a good way to corrupt the database code. I suggest you
unchekc that option and decompile again. When Access gives you the "variable
not defined" error, you now have a lead on what to fix.
Compile on demand is a good way to corrupt the database code. I suggest you
unchekc that option and decompile again. When Access gives you the "variable
not defined" error, you now have a lead on what to fix.
B
Brendan on Comcast.net
Hi RD
I'm certain I'm blowing through the stop. Put a message box before and after
it and both appear.
The problem appears to be PC related and not database related. i.e. I have
the problem on 2/3 pcs. The stop stops on the third, using the same MS
Access DB on all three.
go figger!
Breakpoints don't work either, meaning they don't break execution.
Maybe I've found some kind of eternal motion machine? you can't stop it!
BJC
I'm certain I'm blowing through the stop. Put a message box before and after
it and both appear.
The problem appears to be PC related and not database related. i.e. I have
the problem on 2/3 pcs. The stop stops on the third, using the same MS
Access DB on all three.
go figger!
Breakpoints don't work either, meaning they don't break execution.
Maybe I've found some kind of eternal motion machine? you can't stop it!
BJC