Sudden Crash and weird behavior

L

Les Hauck

Hellllllllllllllp: Using Access 2002(Using 2000 file format) on Win XP Pro,
AutoName Turned Off. (Same Thing was happening in Access 97) When in design
mode, and walking through code, if the Error window pops open on a problem, I
select Debug, check the code and either comment out the problem or correct it
and when I close out the module, the current form and Access just shut down
and dump me out to the operating system. Same thing happens when application
is running and users run into Error Warning and they select with "End" of
"Debug". Also on occassion, when in a form module and using the "DoCmd" or
other object, the parameter options only show for a fraction of a second and
disappear before I can select anything . Any help would be appreciated
 
S

Stuart McCall

Les Hauck said:
Hellllllllllllllp: Using Access 2002(Using 2000 file format) on Win XP
Pro,
AutoName Turned Off. (Same Thing was happening in Access 97) When in
design
mode, and walking through code, if the Error window pops open on a
problem, I
select Debug, check the code and either comment out the problem or correct
it
and when I close out the module, the current form and Access just shut
down
and dump me out to the operating system. Same thing happens when
application
is running and users run into Error Warning and they select with "End" of
"Debug". Also on occassion, when in a form module and using the "DoCmd" or
other object, the parameter options only show for a fraction of a second
and
disappear before I can select anything . Any help would be appreciated

Sounds like database corruption. Try making a new db and importing
everything into it.
 
T

Tony Toews [MVP]

Les Hauck said:
Hellllllllllllllp: Using Access 2002(Using 2000 file format) on Win XP Pro,
AutoName Turned Off. (Same Thing was happening in Access 97) When in design
mode, and walking through code, if the Error window pops open on a problem, I
select Debug, check the code and either comment out the problem or correct it
and when I close out the module, the current form and Access just shut down
and dump me out to the operating system.

That could be corruption or who knows what. Try stopping the code
execution, compiling and saving the module first though before closing
the module.. Also turn off Compile on Demand in VBA Tools >>
Options.

On the subject of compiling I added the compile button to my VBA
toolbar. See
http://msmvps.com/blogs/access/arch...tton-every-few-lines-of-vba-code-i-enter.aspx
for more details.
Same thing happens when application
is running and users run into Error Warning and they select with "End" of
"Debug".

You should have error handling in every code module so users never,
ever see End or Debug.
Also on occassion, when in a form module and using the "DoCmd" or
other object, the parameter options only show for a fraction of a second and
disappear before I can select anything . Any help would be appreciated

You have a timer event running on another form. I would suggest
distributing MDEs to your user and turning on the Timer only when the
code is executing in an MDE. So as to not cause problems when you are
working in the MDB.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top