Hi,

I wrote some code to call a function in an Access database by
Application.Run. It worked perfect. Now I put the same code into another
Access database and try to do the same.

When I come to "Application.Run", a second window pops up (with the
second database) and code execution stops. The only way to continue is,
open the code module and hit F5 to resume execution.

It seems this is a de{*filter*} problem. Somehow the two Access instances
must communitcate and decide that I probably want to debug right now.

Did anybody have the same problem and knows a workaround?

Thanks, Christoph

Does the code halt at a location where you previously had a breakpoint set?
I've only been working with Access 2000 for a few months, but I've already
seen phantom breakpoints in local code:  code halting at places where I had
previously set and then removed breakpoints.  I was able to get rid of them
by Debug->Clear All Breakpoints, followed by Debug->Compile.  If I recall
correctly, it didn't always work the first time, but so far it has
eventually worked, so you might try that with your second database.

--
Dirk Goldgar
www.datagnostics.com

(to reply via e-mail, remove NOSPAM from address)

Hi Dirk,

Dirk Goldgar schrieb:

It worked perfectly, thanks. You saved my project, that should run
tomorrow :-)

Christoph