ACC97: Changing Project Name Doesn't Enable Compile Menu Command

Last reviewed: August 29, 1997
Article ID: Q168882
The information in this article applies to:
  • Microsoft Access 97

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

When you compile a module that you are using by clicking the "Compile and Save All Modules" command on the Debug menu, the Compile menu commands appear dimmed (unavailable) after the module has been compiled. If you change the Project you are using and then try to compile the project, the Compile menu commands remain dimmed.

CAUSE

The Debug menu is not reset when you change the Project you are using. Therefore, the Compile menu commands remain dimmed.

RESOLUTION

Close the module, close the database, and then reopen both the database and the module. Then the Compile menu commands will be available on the Debug menu.

MORE INFORMATION

Steps to Reproduce Behavior

  1. Create a new blank database.

  2. Open a new module.

  3. On the Debug menu, click "Compile and Save All Modules." Save the module as Module1. The Compile menu commands on the Debug menu now appear dimmed.

  4. On the Tools menu, click Options, and then click the Advanced tab.

  5. Change the Project Name, click Apply, and then click OK.

  6. On the Debug menu, note that the Compile menu commands still appear dimmed.

REFERENCES

For more information about compiling a project, search the Help Index for "projects, testing if compiled," or ask the Microsoft Access 97 Office Assistant.

Keywords          : kbprg PgmOthr
Version           : 97
Platform          : WINDOWS
Hardware          : x86
Issue type        : kbprb
Solution Type     : kbworkaround


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: August 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.