Debugging Access 2000 mdb file in Access 2003

G

Guest

Hi,

I have a mdb file with a lot of forms developed in Access 2000. We have
upgraded to Access 2003 and I need to debug the code in order to find errors.
But I cannot get the debugging to work. I start the mdb file and the main
form comes up. I then go into the visual basic editor and place a breakpoint
i the code of a button click and then press the button. At this time I
expected that the execution would stop and let me step through the code but
this doesn't happen. The code executes without breaking. What am I doing
wrong? And yes I am sure that I have the breakpoint in the right place:)

Is there a setting I've missed or is there a compatability problem with 2000
and 2003?

I have tried to create a dummy project in 2003 and using breakpoints to stop
execution and it worked fine.

Please help.

Best regards
PÃ¥l Eilertsen
 
G

Guest

PÃ¥l,

I've seen this before with converted 2000->2003 .mdbs.
The only cure I found was to create a brand new 2003-version .mdb file and
import *everything* from the converted database into it, and *voila* it
should suddenly all start working in the new .mdb.
It seems to be some sort of subtle database corruption problem.

- Mark
 
G

Guest

Hi,

Thanks for your answer. But actually I worked it out and it was quite easy
(I might be a dummy:)). I just went for Tools/Startup and checked the "Use
Access Special Keys". After that debugging worked like a charm.

Best regards
PÃ¥l Eilertsen
Norway
 

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

Similar Threads


Top