Event Procedures stopped working

[dbhacker]

I converted a DB from Access 2003 to Access 2007. First the Switchboard was
corrupted so I remade the switchboard. Everything else seemed fine ( I
tested all buttons/procedures within the user interface). This AM I opened
the DB again and the Event Procedures stopped working. It is interesting
because the Macros DO work but the Event Procedures do not. These are the
same Event Procedures that worked fine yesterday evening. I recompiled the
Event Procedures and it still does not work. Any suggestions?

 

[Dirk Goldgar]

I converted a DB from Access 2003 to Access 2007. First the Switchboard
was
corrupted so I remade the switchboard. Everything else seemed fine ( I
tested all buttons/procedures within the user interface). This AM I
opened
the DB again and the Event Procedures stopped working. It is interesting
because the Macros DO work but the Event Procedures do not. These are the
same Event Procedures that worked fine yesterday evening. I recompiled
the
Event Procedures and it still does not work. Any suggestions?

Given Access 2007's enhanced security, it may be that VBA is disabled in
this database. Is it in a trusted location? When you open it, do you get a
warning about disabled code? Such warnings can be easy to overlook.
Usually the answer is to put the database in a trusted location, as defined
in your Trust Center settings.

 

[Linq Adams via AccessMonster.com]

As Dirk said, code does not run in 2007 unless your database resides in a
folder that has been declared a “trusted†location.

To trust your folder, click:

Office Button (top left)
Access Options (bottom of dialog)
Trust Center (left)
Trust Center Settings (button)
Trusted Locations (left)
Add new location (button)

 

[Dirk Goldgar]

As Dirk said, code does not run in 2007 unless your database resides in a
folder that has been declared a “trusted†location.

I'm pretty sure, though I can't check it right now, that one can explicitly
trust a specific database. But trusted locations are much simpler.

 

[dbhacker]

It was indeed a security issue. Thanks for the detailed instructions on how
to put the DB in a "trusted" location! Everything is working great.

 

[manorero]

Experiencing simular issues. Created dabase with vb events on my desktop.
Copied db to another users p.c. and events stoped working. Command button in
design view still shows events and can open VB editor from the buttons event
in design view. Db file location is trusted, but events still not working.
Any words of wisdom will be n=much appreciated.

 

[Dirk Goldgar]

Experiencing simular issues. Created dabase with vb events on my desktop.
Copied db to another users p.c. and events stoped working. Command button
in
design view still shows events and can open VB editor from the buttons
event
in design view. Db file location is trusted, but events still not
working.
Any words of wisdom will be n=much appreciated.

If this is under the Vista operating system, make sure that the database
isn't blocked: right-click the database file, open its property sheet, and
see if there's an Unblock button. If there is, click it.

If the database isn't blocked, and you're sure the database is in a trusted
location, but the VBA code still doesn't run, make sure that there are no
broken references. References to external libraries can be broken when a
database is moved to another PC. See if Doug Steele's instructions here
help:

http://www.accessmvp.com/djsteele/AccessReferenceErrors.html