Access prompting for DB Password when none exists

[Niko]

I have an Access 2003 database that uses an MDW for security. It is
also signed with a VBA code-signing certification, in case that
matters. There is *not* a database-level password applied.

I've sent the database and mdw to another user who needs to make some
changes to some reports. She logs in successfully via the mdw (using
the same username/password that I use regularly myself), and can see
the database objects, but when she tries to work with anything, she's
getting the message:

"Microsoft helps protect this Visual Basic for Applications Project
with a password. You must supply the password in the Visual Basic
Editor before you can perform this operation."

I have never gotten this message in my own development, and it seems
to be referring to a database-level password, which does not exist in
the database.

Anyone have any idea what else this message might be referring to?
Could it be the code-signing? I thought that her making changes
without the code-signing certificate would just invalidate the code-
signing already on there, not stop her from making the changes at all,
but I can't think of any other difference between her development
environment and mine.

 

[Joan Wild]

"Microsoft helps protect this Visual Basic for Applications Project
with a password. You must supply the password in the Visual Basic
Editor before you can perform this operation."

I have never gotten this message in my own development, and it seems
to be referring to a database-level password, which does not exist in
the database.

In VBE, Tools - Properties - Protection Tab - a password was set there?