Autoexec drops into debug

[Guest]

I have a database that has been in use by the department for some time
without problems.

We recently added a team member who needs to be able to do some development
work on the database. As I had the developers copy of the database, I moved
it to a common drive that we can both access and keep individual copies to
work on (we have a check out process between ourselves). When he goes to
open the database from his copy or the common one we draw from, the autoexec
drops into debug. However, when he opens the public copy everything works as
expected.

If I open our shared copy, I have no problems. I've checked that he has
proper rights to the folder where we keep the database. The common copy is
not passworded or otherwise protected.

Any thoughts would be greatly appreciated.

TIA

John

 

[Steve Schapel]

John,

Does he have the same version of Access installed on his computer?

Can you give some more explanation as to what you mean by "drops into
debug"?

 

[Guest]

Yes we have the same version of Access (2003). Run the autoexec macro and
the IDE opens with execution stopped at the first statement in the first
procedure that the autoexec calls.

 

[Steve Schapel]

Yes we have the same version of Access (2003). Run the autoexec macro and
the IDE opens with execution stopped at the first statement in the first
procedure that the autoexec calls.

... which is?

 

[Steve Schapel]

John,

Just guessing here, but are you using RunCode action in your AutoExec macro?

 

[Guest]

Yes

John,

Just guessing here, but are you using RunCode action in your AutoExec macro?