Access 2003 Debugger Woes

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Atlas - 14 Mar 2005 12:37 GMT

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?

Reply to this Message

Allen Browne - 14 Mar 2005 14:24 GMT

No, that is not normal.

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

Signature

Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

> 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?

Reply to this Message

Atlas - 14 Mar 2005 19:50 GMT

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?

> No, that is not normal.
>
[quoted text clipped - 3 lines]
>> Sometimes when setting breakpoints it "jumps" somewhere else....is it
>> normal?

Reply to this Message

Wayne Phillips - 14 Mar 2005 23:06 GMT

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
http://www.everythingaccess.com

> I never use timers.
>
[quoted text clipped - 9 lines]
> >> Sometimes when setting breakpoints it "jumps" somewhere else....is it
> >> normal?

Reply to this Message

Atlas - 15 Mar 2005 16:14 GMT

>I think you should try decompiling the VBA project.
> Lots of 'strange quirks' in VBA can be caused by compilation errors which
[quoted text clipped - 6 lines]
>
> Wayne Phillips

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

Reply to this Message

Allen Browne - 15 Mar 2005 16:46 GMT

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"

Signature

Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

>>I think you should try decompiling the VBA project.
>> Lots of 'strange quirks' in VBA can be caused by compilation errors which
[quoted text clipped - 14 lines]
>
> Thanks

Reply to this Message