Access 2003 Debugger Woes

  • Thread starter Thread starter Atlas
  • Start date Start date
A

Atlas

Even the VBA debugger doesn't look to me so smart. Same to you?
Sometimes when setting breakpoints it "jumps" somewhere else....is it
normal?
 
No, that is not normal.

There must be another factor at work, such as the Timer event of a form.
 
I never use timers.

But this starnge code "jumps" aren't occuring very often. To be honest IMHO
they happen when offending code is run. In some rare occasions, without the
debugger running, I have some unexpected crashes, so that may be tha case?
 
Wayne Phillips said:
I think you should try decompiling the VBA project.
Lots of 'strange quirks' in VBA can be caused by compilation errors which
get worse over time.

Try the following link which describes how to do the decompile in Access.
http://www.granite.ab.ca/access/decompile.htm

Regards,

Wayne Phillips
Click to expand...


Wayne,
usually every week or two of development I create a new empty .adp project
and import everything into it. It shrinks down and speeds startup.

Is it the same as decompile?


Thanks
 
No.

Importing as you describe does solve some kinds of corruption, but not the
kind of VBA corruption that a decompile addresses.

Decompile a copy of the database by entering something like this at the
command prompt while Access is not running. It is all one line, and include
the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
 
Back
Top